I accidentally sent this to Jürgen only. Here it is for the rest of the
list.
Regards,
Elias
-- Forwarded message --
From: Elias Mårtenson loke...@gmail.com
Date: 23 Apr 2014 01:13
Subject: Re: [Bug-apl] 2 questions wrt editing my programs
To: Jürgen Sauermann
Thanks Jürgen Elias for your responses. I will explore both approaches.
In fact I have downloaded Emacs for OS X from http://emacsformacosx.com/ but
not yet installed it.
As a long time user of BBEdit, a great text editor for Mac, I've also
downloaded the free TextWrangler app.
It's also from
Just for the sake of discussion, and not because I specifically object
to any of the proposed library bindings: It'd be nice to see some
motivation for mapping new libraries into/onto APL.
I know that Dyalog APL has all of the features proposed by Elias (and
more). I don't, however, assign much
I've pushed apl-cf to Github.
The only change (since the last tarball posted to bug-apl) is the
addition of a README.md file.
https://github.com/TieDyedDevil/apl-cf
Greetings,
Your email sparked many thoughts. Not that my opinion necessarily counts
for anything, I think this should be GNU APL's priority list:
1. Fix all known bugs and portability issues as they are discovered.
2. Support all of APL's standard defined features (i.e. trace, stop, etc.)
Thanks! Really appreciate it!
--blake
On Tue, Apr 22, 2014 at 6:53 PM, David B. Lamkins dlamk...@gmail.comwrote:
I've pushed apl-cf to Github.
The only change (since the last tarball posted to bug-apl) is the
addition of a README.md file.
https://github.com/TieDyedDevil/apl-cf
Blake said:
This means creating a quad function to load, execute, and interface with
shared libraries (so/dll/etc).
It also means standard ways of communicating data back and forth
clap clap clap. +1.
That's basically the idea of what we did at IPSA.
As for the file system it was built
