Re: [Modeling-users] ModelMasons refactored
Status: Abandoned
Brought to you by:
sbigaret
From: Mario R. <ma...@ru...> - 2003-04-21 14:37:50
|
On lundi, avr 21, 2003, at 15:02 Europe/Amsterdam, Jerome Kerdreux wrote: > On Mon, Apr 21, 2003 at 02:51:46PM +0200, Sebastien Bigaret wrote: > >> Mario wrote: >>> Just a minor comment, w.r.t. naming of the generated files/classes. >>> I feel that: >>> >>> a) "Base" is probably not the best name extension to use, as it has >>> a well-known generic meaning, and in addition it says nothing about >>> the "volatility" of these generated files/classes. Better names would >>> be something like "Auto" or "Gen" or "mdl" or "pom" or "morfy" ... >> >> Reasonable too. What about 'Autogen'? Since we're going this way I >> guess >> that models (xml/py) should be moved to that directory too, so that >> everything that is overwritten when generating the code clearly falls >> in >> the dedicated directory. > > Hum I want to maintain a reference to the fact that this came from the > modeling. Cause i use some ORB here and it generate a lot of code too > so 'Autogen' hurt me a little . (same in glade too) > I prefer the previous one 'Mdl' or something else. Don't understand. Why does AutoGen give you a problem and Base does not, as far as other 3rd party generated code goes ? >> Mario> b) It is unnecessarily repeated -- what is the point of naming >> Mario> all the classes in the "Base" sub-package also with "Base"? >> Mario> Wouldn't it be more convenient to name only the sub-package? >> E.g. >> [...] >> >> No problem; since we forget about 'Base' as a package it's a nonsense >> to >> keep it here. > > > Hum i'm not really clear about this, but i think this can generated > namespace colision . mainly in the 'working' module Well, it is true if you import it directly into the local namespace. However, i fell it is a lot of clutter to keep repeating the prefix (or postfix) for each file. What is the point of having a namespace if not to avoid having to do such things? Besides, instead of: import AutoGen class Folder(AutoGen.Folder): ... no-one will ever stop you from doing: from AutoGen import Folder as FolderBase class Folder(FolderBase): ... Except yourself, of course ;) Cheers, mario |