This sounds good - and if those of us who wrote our own 1!: 2!: scripts 20 years ago (and never require 'files") are able to easily retrofit them into the cd scheme, then I'm all for making the changes being proposed. Sounds like exciting new possibilities.
At 11:17 -0400 2009/10/22, Eric Iverson wrote: >The current jconsole has compiled C code that does >fgets/fputs/readline/isatty and etc. This could stay this way as it seems to >work and isn't a source of problems. > >But with the new JFE it would be possible to implement all that in J with cd >calls. That would mean that jconsole would become a dead simple binary that >had no host dependent code or any calls to host services. jconsole would >become je and would just load the JE shared library and with a suitable >starting script would provide a console front end as defined by a J >programmer. > > >On Thu, Oct 22, 2009 at 10:33 AM, bill lam <[email protected]> wrote: > >> On Thu, 22 Oct 2009, Raul Miller wrote: >> > I think that your stdio jfe will be useful for several reasons: >> >> I'm not quite understand what will the difference between stdio jfe >> and current jconsole. >> > > -- ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
