As Dan has pointed out, many of these concerns exist for mapped files. As such, making clear definitions for the complications is more than just an academic exorcise. Names created to support mapped files are kind of odd balls. The violate many of the guidelines for good programming practices.
Defining these attributes to regular J names opens up many possibilities including simplifying and cleaning up mapped files. Also, this may help address the problems of accessing files on clients and servers as J7 evolves. On Fri, Jan 22, 2010 at 11:48 AM, Dan Bron <[email protected]> wrote: > Roger wrote: > > The complications are: > > - do you permit erasure of a single assignment name (AS1)? > > - do you permit destruction of a locale containing an AS1? > > - do you permit an AS1s to be mapped to a read/write file? > > - do you permit a global AS1 to be shadowed by a local name? > > - need a facility to tell you what all the AS1s are > > - need a facility to tell you whether a name is an AS1 > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
