What I was thinking was that UTf8 characters be allowed as part of a name. But you're right. Doing that does open several cans of worms. I haven't looked at UTF that closely. I know that there are UTF characters that are not part of the ASCII character set that represent numbers. Are there also some that represent white space? And if UTF characters were opened up for names would this prevent the use of those characters as primitives at some future date? Backward compatibility can be such a pain at times! On Thu, May 21, 2009 at 12:56 PM, Raul Miller <[email protected]> wrote:
> On Thu, May 21, 2009 at 1:11 PM, Don Guinn <[email protected]> wrote: > > What about having J names allow UTF8 characters instead of being limited > to > > ASCII characters? > > We can not treat all characters identically: > > Which characters should be treated as letters? Which should be treated as > digits? Which should be treated as tokens? Which should be treated as > whitespace? How will this effect code written with this version of J when > later versions of J become available? > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
