Name Fussiness Again
-
Oakman wrote:
I was thinking of sending one out - did you write one already?
Yes, i posted it in The Lounge last night. A Soapboxy rant, full of rambling stories, dubious correlations, and tales of substance abuse. :-\
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
Ilíon wrote:
and a LongshoreMenUnion and a WarehouseUnion
:laugh: You know, I read that as WhorehouseUnion. I hadn't realised that prostitues had formed a union.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
I hadn't realised that prostitues had formed a union.
International Union of Sex Workers "Workers of the world, unite and fight! You have nothing to lose but your er...uh..."
Jon Smith & Wesson: The original point and click interface
-
I am designing a set of objects that perform the same data export task, but differ in versions, or implementation. They share fixed, common aspects I think fit well in a base class. I'm having trouble naming these objects; the best I've got so far is ExportEngine, Exporter just doesn't seem right. Any suggestions?
Pits fall into Chuck Norris.
'John'is always a good startng point. You can develope from this 'big John', 'fat John' and so on describing objects with names that, even if they dont describe exactly what their function is, do at least make them familiar, which is half the battle.
Morality is indistinguishable from social proscription
-
Why in the soapbox? Anyway, name the common elements something (ie BradysFormat) and then call it a Writer as in BradyFormatWriter.
martin_hughes wrote:
Why in the soapbox?
Sorry, I thought I was in the lounge. :-O
Pits fall into Chuck Norris.
-
Sounds like you need an ExporterFactory, or possibly an ExporterProvider and ExporterProviderBase.
Deja View - the feeling that you've seen this post before.
Thanks Pete, I think I'll go with ExportTestProvider, as the class uses an Export class to perform test exports.
Pits fall into Chuck Norris.