On Mon, May 27, 2013 at 10:58 AM, Murray Eisenberg <mur...@math.umass.edu> wrote: > On 26 May 2013 19:41:36 -0400, Raul Miller <rauldmil...@gmail.com> wrote: > >> One issue is that J's ~ convention is not the OS convention, so you >> will need to deal with that. If you are not on windows (which is >> probably the case if you are using a ~ OS convention), you can use >> >> HOME=: 2!:5'HOME' >> . . . > > Why wouldn't -- or shouldn't J know about the OS convention "~" for OS X as > well as for Linux (and other Unix-derived systems)? I thought recognizing the > OS is part of the start-up sequence for J.
I am not sure. If we are talking about prepackaged functionality, that's probably a question for Eric Iverson. That said, I'll note that the ~ conventions are implemented in unix shells which were not particularly relevant during much of J's design. And, by this I mean that J has a platform agnostic history but also that a significant part of J's design happened in the 50s and the 60s (though it's true that another significant part happened in the 80s and 90s). > I do know about the potential clash with the way ~ is mused as part of the > argument to jpath. But why can't/shouldn't J allow ~ as part of a file path > if jpath is not being used? It can allow this, of course. jpath is just a function. You could write a unixpath that does ~ expansion. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
