[Moose-dev] Re: Issue 744 in moose-technology: SmalltalkImporter should be renamed SmalltalkExtractor

Comment #5 on issue 744 by tudor.gi...(a)gmail.com: SmalltalkImporter should be renamed SmalltalkExtractor http://code.google.com/p/moose-technology/issues/detail?id=744 This means that I veto this change in the main version of Moose. I gave you my reasons. Importer denotes going from an external source to the model. It's a clear meaning. And it fits in the metaphor that we have an importing step. If we introduce another term we will say, an importing/extracting step which is not nice. If you want to stress that it has to do with code, you can say SmalltalkCodeImporter, but to me, it really is very clear what SmalltalkImporter stands for. Now, I do not think that you should need forking, but if you insist, of course, I cannot stop you.