From: alex b. <en...@tu...> - 2001-07-08 18:11:21
|
> Hmm, for the moment I don't see a reason. But with ZendEngine 2.0 it may be > supportet but then they would be specially marked i guess (private > $varname). well, looks like private vars will be supported, so a naming standard is relevant. > So a special naming convention isn't really neccessary. > But there should be an convention that classvars should only be accessed by > getVarname(), setVarname() methods. So this implies all that all varnames > without an accessor are private ones. Hmm, I don't know if I agree with that. What does it get you? i.e. why not, $ClassName->var ? is there a reason to create a method name to match each public class var? > - multiple Inheritances* > - private member vars* > - static member vars > - exception handling (throw, try, catch) no shit? > - destructors > - new objects model (similar to java, variables contina object handles > instead of the objects) > - improved OO Apis (java objects, com) > - internationalization (multilingual error messages, unicode, non western > charsets) Yes, this last one is a good step. Everything is pretty ISO-8859-1 heavy, it will be good to get some more mature charset support. in any case, doesn't look like varnames are a big controversy :) _a |