From: David Simmons Date: 2001-11-25T05:18:35+09:00 Subject: [ruby-talk:26362] Selector Namespaces: A Standard Feature for Smalltalk? 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