On 05/22/2011 10:56 PM, hgc2002 wrote: > No, there is no warning in console about it. > Then I suppose this is a non-recommendable practice. > If this is true, I can't understand why. It's a very nice flexibility. > I don't see why it's forbiden in build version.
It's the nature of private variables. The name private means just that: they are private, and not supposed to be used anywhere outside the class in which they were defined. This is true for most object oriented languages and qooxdoo is no exception. > In any case, well, it does not look bad to have a more restrict process in > the build. The reason that it doesn't raise any errors in the source version is a technical one. Javascript has no support for private variables (everything is always public) so nothing can stop you from breaking the rules and ignoring the private status. > But this should be included in the documentation, just in case. There is a mention (although brief): http://manual.qooxdoo.org/1.4.x/pages/core/oo_feature_summary.html#access Regards, Marc ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
