|Subject:||Re: [Bug-apl] question on host and few other things...|
|Date:||Sun, 30 Mar 2014 12:06:44 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130330 Thunderbird/17.0.5|
please see my answers inline below...
On 03/29/2014 09:08 PM, Harteg Wariyar wrote:
I am not familiar with Apple products, but maybe Peter's nice document
doc/APL-on-Macintosh.pdf could have helped?
I believe the above ⎕ functions are from some other APL interpreter.
GNU APL has only implemented the ⎕ functions defined in IBM APL2 and
in the ISO standard.
In IBM APL2 you would do things like the above via AP100 (see src/testcases/AP100.tc
for an example.
In GNU APL you also have the FILE_IO native function, see src/testcases/FILE_IO.tc
for an example.
Same as above. Currently you can )DUMP a workspace in a format that can be read back
with apl -f. I could think about extending )COPY so it understands .apl files from )DUMP.
I have added that to my TODO list.
Otherwise, FILE_IO is the way to go.
Sounds like wrong ESC sequences for colors. Check your preferences file.
I am rather sceptical of non-standard "improvements" of APL. I have seen many such extensions
in other interpreters and languages. Very few of these extensions have really convinced me,
though. I also believe that too many different extensions in different APL interpreters split an
already small community of APL users into even smaller fractions. I understand that in the past this
was (thought to be) needed by commercial vendors to distinguish their APL interpreter from those of
their competitors. But the overall effect of that may have harmed APL more than it has helped.
So, don't expect too much from GNU APL in that direction.
|[Prev in Thread]||Current Thread||[Next in Thread]|