First of all, I'm a newcomer to APL and even though I've hit 40 I feel
somewhat like the new kid on the block. :-)
I haven't advocated plenty of new quad-commands or changes to the core
language (although there are certainly a few of those that I'd like to see
too, but I respect Jürgens wishes
Hi,
I really appreciate the discussions on this because I believe
there is a open issue (libraries and how to provision them).
1. First of all I would like to share my current point of view regarding
⎕-functions and
-variables. The (only ?) good thing about them is that they are ready to
be
Hi Blake,
I believe your 1, 2, 3 below is exactly the current priorities of GNU
APL and 3. is already
present.
We use shared libraries for extending APL so you don't need an extra
developer lib
for that. The only thing needed is a header file declaring the functions
available in
GNU APL
Hi ,
don't wait any longer for ⎕host. Its already there - called popen() in
FILE_IO.
see man popen how to use it.
/// Jürgen
On 04/23/2014 03:33 PM, enz...@gmx.com wrote:
On Tue, 22 Apr 2014 22:14:21 -0400
Peter Teeson peter.tee...@icloud.com wrote:
Blake said:
This means creating a
Hi,
I see. I have changed the test in configure so that it checks whether the
compiler is g++ rather than whether it accepts -rdynamic. SVN 221.
That should also avoid the same warning in Solaris.
/// Jürgen
On 04/22/2014 07:01 PM, Peter Teeson wrote:
Hi Jürgen:
Gandalf:~ pteeson$ man gcc
No
