I don't think locale names can contain underscores:
cocurrent 'a_b'
|ill-formed name: a_b
| cocurrent'a_b'
If you are finding some place that accepts underscore in locale name,
please report it as a bug.
Even if they were allowed, how would you use them?
a_b =: 6
a_b_base_
6
No way to refer to locale b_base .
Henry Rich
On 4/8/2017 11:50 AM, 'Pascal Jasmin' via Programming wrote:
just realized that locale names are allowed to have inner underscores.
so the name collision problem is solved by sublocale_tara_?
and then the filtered "toplevel" locales could simply be those without
underscore if the convention is followed.
The sublocales of tara are the '_tara' +./@:E. locales by convention.
good enough?
________________________________
From: Henry Rich <henryhr...@gmail.com>
To: programm...@jsoftware.com
Sent: Saturday, April 8, 2017 11:42 AM
Subject: Re: [Jprogramming] locales with adverbs and conjunctions?
Could nesting locales be achieved by a convention that says that nested
locales have names like
"outer___inner" where I am using 3 underscores ___ to represent some
unique string?
The name-collision problem would then be solved except at the highest
level. I don't see how the highest level can be solved without a
coordinating authority. Boulder would still have to back off from biff.
What is achieved besides reduction in collision potential?
A query for locale names could suppress nested locales by default.
Currently, when I list the locales, I get a zillion that start with
'dissect'. It would be nice to see just the top-level locale.
Henry Rich
On 4/8/2017 6:43 AM, Raul Miller wrote:
So, for example, instead of an addon like tara requiring 18 locales,
it would occupy one locale which contained the others it needs.
So, for example, if the Boulder international film festival at some
point has a J programmer that releases some little addon of relevance
to them, we are less likely to need to yell at them that the locale
'biff' is already taken.
Not a pressing need at the moment, (and maybe never) but I like to
plan ahead (though perhaps J will never be popular enough for this to
be an issue?).
Thanks,
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
