> > But, it seems to me that C::A > > should be the one prefixing all its variables as "__C_A__" so that it is > > transparent to the applications extending C:A? > > If you have the choice > > between thousands of users having to prefix their variables, or C:A doing > > it, wouldn't it make sense for C:A to do it?
I just wanted to add one more thing to this. To follow your suggestion, what would you do if you or someone else wanted to subclass your own module? I guess you are going to have to prefix all your variables with __C_A__M_F__ so that you don't conflict with any potential subclasses (and what about subclasses of those subclasses). See how that logic breaks down? It needs to be the other way around. The parent class does what it wants and explains the convention, and subclasses have to make sure they comply. Not the other way around. Cheers, Cees --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
