Here is an incentive for classic Smalltalk evolution...

Selector namespaces are a dynamic language unification of
classic-static-language notions of public, private, and protected. They are
most important for their ability to address and resolve fragile-base-class
issues and traditional (3rd party) late (just-in-time) integration
conflicts/fragility.

As many [comp.lang.smalltalk] readers here know, SmallScript (an extended
dialect of Smalltalk) supports selector namespaces from its QKS Smalltalk
heritage where they first appeared in the Win32 version in 1996-1997. They
are a fundamental feature of the SmallScript language and its underlying AOS
Object Model services. The .NET implementation of the AOS Object Model
enables dynamic languages to support selector namespace facilities on the
Microsoft .NET architecture.

What you may not know is that the ECMAScript standards group has recently
(2001) decided to incorporate selector namespaces. Netscape will be making a
reference/review implementation (JavaScript 2.0) available in coming months.
JavaScript 2.0 has a wealth of powerful new features that elevate it to a
new level as a language. As many people know, JavaScript is arguably one of
the most widely used scripting languages for the web. Its upcoming feature
set and evolution will have a profound impact on other languages operating
in its same paradigm/space.

Standard
    http://www.mozilla.org/js/language/

Slides:
    http://ll1.mit.edu/horwat.ppt

-- Dave S. [www.smallscript.org]


begin 666 Dave Simmons.vcf
M0D5'24XZ5D-!4D0-"E9%4E-)3TXZ,BXQ#0I..E-I;6UO;G,[1&%V:60[00T*
M1DXZ1&%V92!3:6UM;VYS#0I.24-+3D%-13I$879E(%,N#0I/4D<Z4VUA;&Q3
M8W)I<'0@3$Q##0I54DP[5T]22SIH='1P.B\O=W=W+G-M86QL<V-R:7!T+F]R
M9PT*14U!24P[4%)%1CM)3E1%4DY%5#ID879I9"YS:6UM;VYS0'-M86QL<V-R
J:7!T+F-O;0T*4D56.C(P,#$Q,3(T5#(P,3 R-UH-"D5.1#I60T%21 T*
`
end