Hmm. I've always thought that this was how J normally process variable assignments.
I sort of rely on this since I would normally have a minimum of 2 locales. One is for the global variables and methods which is "z" and "base" which is my default locale. I would sometimes reference the base locale by going: avariable__=. 'Percy Jackson is the son of Poseidon' -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of bill lam Sent: Tuesday, January 19, 2010 10:04 AM To: [email protected] Subject: Re: [Jchat] global local in locale mar, 19 Jan 2010, Zsbán Ambrus skribis: > On Mon, Jan 18, 2010 at 2:37 PM, Don Guinn <[email protected]> wrote: > > Explicitly including the locale in a name makes a local copula (=.) a global > > assignment. [...] > > It also lets you get > > around the error message about making an assignment of a global name when > > the name already exists as a local name. > > You don't need this feature for that, for assigning to a name with > locale with the =: copula also lets you do that. For example, I concur. That this 'feature' can also be classified as a bug because it mixes =. (which must be local) and name inside a locale (which must be global). -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
