Newsgroups: comp.lang.apl
Path: watmath!watserv2.uwaterloo.ca!torn!cs.utexas.edu!uwm.edu!spool.mu.edu!uunet!s5!hui
From: hui@fid.morgan.com (Roger Hui)
Subject: Re: Change in the effect of (1!: 1) 1 in J 6.
Message-ID: <1993Jan17.201837.14485@fid.morgan.com>
Organization: Morgan Stanley & Co., New York, NY
References: <memo.872077@cix.compulink.co.uk>
Date: Sun, 17 Jan 1993 20:18:37 GMT
Lines: 19

Paul Moore writes:
 
> Essentially, yes. I am thinking of file processing applications, where I
> don't want to be constrained to files which will fit in memory. I don't have
> a concrete example, as I do not have a specific need at present. I was
> really only commenting on the inconsistencies in the interpretation of 1!:1
> (line-at-a-time on standard input, full-file on other files) which surprised
> me in such an otherwise highly regular language as J. I am also suggesting
> that line-at-a-time is often what is wanted CONCEPTUALLY even if it can
> usually be implemented via read-the-whole-file-and-split.

1!:11 and 1!:12 permit reading/writing part of a file.  These have 
been available since many versions ago.

1!:1(1) was fixed when 0!:4 and 0!:5 were added and 0!:2 and 0!:3 
were fixed.  The previous version can get some nasty errors when 
scripts are nested within scripts.  There are no plans to enhanced 
1!:1(1) as the line-by-line-terminal-input-to-programs style of 
interaction is obsolete.  Try Windows.
