Joe Tibollo wrote: > scripts like VB but it has workspaces and debugs in a manner > more nearly akin to APL. It's that pedigree that makes J > so powerful. But, with power comes responsibility. What > results is an explosion of names. Both in the workspace > and in the form of files on disk. This can result in greater > complexity and therefore more work and a steeper learning > curve.
>From this I'd be inclined to conclude that you're not aware of most of the names in VB. (Or, perhaps you're using an ancient version of VB which doesn't have very many names in the environment?) In VB .Net, a typical script might have numerous namespace references. For example: Imports System Imports System.Collections Imports System.ComponentModel Imports System.Text Imports System.Web Imports System.Web.UI Imports System.Web.UI.WebControls Imports System.Web.UI.HtmlControls Imports System.Xml Imports System.Xml.Xsl Imports System.Xml.XPath Imports System.IO Imports System.Configuration Imports System.Text.RegularExpressions Imports Microsoft.VisualBasic Each of these name spaces might have many classes (which correspond, roughly, to J's locales), and each of these classes might in turn have many names of various sorts... In my opinion, you have far, far more names to deal with in the context of VB than in the context of J. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
