> And it's rather trivial for a conjunction to access the state of its native locale (just be explicit about that).
It's trivial for static locale, but fails for numbered locales derived with conew, because the code will never have access to the number unless the caller passes it. -- which is the workaround I've used. In terms of OOP (numbered locale) use, its not fair to say it should be avoided for J. If a table, file, database, socket connection are usefully encapsulated in a locale, then the concept that you might want to have more than one of these in your program makes numbered locales relevant. potential modifiers defined for, say a file, locale might set a local verb for how to define an item in that file, and then from that define means to add, retrieve, delete items in a way that the caller doesn't need to care about, or correctly pass on each call to other functions. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
