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
