I’ve been thinking about creating a class that handles importing and exporting of data, and I feel that naming it FooImporterExporter might look too long, I wan’t to see if there’s a name convention that I could use to name it.
These are some of the names I think would be appropriate:
FooProcessorFooPorter/FooPort– ( as Import/Export comes from trading goods in a Port )FooTrader
5
The name of the class should make the responsibility of that class obvious. FooProcessor is ambiguous; FooPorter and FooTrader are each a cute play on words.
FooImporterExporter tells the reader exactly what the class does, it imports and exports Foos.
Having said that, you really should split it into two class, FooImporter and FooExporter. The reason it is a pattern that Java and other languages follow is because they are respecting Single Responsibility Principle.