Some time back, there was an interesting discussion of whether Unicon should support "private" class variables and methods. If you recall, an earlier default "private" semantics had been removed because it was inefficient, and un-Iconish. Also if you recall: the privacy interesting discussion on this list had substantial disagreement and valid technical points on both sides of the issue.
This note is to let you-all know of my intention to introduce optional "private" syntax for classes. As an optional non-default feature, such syntax will not clutter up programs that don't use it, and I believe it will be genuinely useful on larger projects. The syntax will appear initially (i.e. real soon) as a documentation aid; enforcing semantics will come later. So, if anyone has strong reasons not to do this, or specific suggestions or requests as I do this, speak now or forever hold your peace. :-) Clint [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
