Hi David,
thanks, included in SVN 346.
/// Jürgen
On 06/27/2014 06:39 PM, David Lamkins wrote:
]LIB still ignores symlinks. Patch attached.
On Fri, Jun 27, 2014 at 7:43 AM, Juergen Sauermann
mailto:juergen.sauerm...@t-online.de>>
wrote:
Hi David,
thanks, fixed in SVN 343.
Hi David,
this means that an apl value without an owner was detected, but that
no more info about that value is available because the value history was
disable.
The history of a value can be enabled with *./configure
VALUE_HISTORY_WANTED=yes*
or with *make develop*.
If this happens when *)SI
Hi Elias,
thanks, I have put Unix sockets for shared variables onto my TODO list.
It is easier to first replace the UDP sockets with TCP sockets (reducing
the total number of sockets used) and then change the socket type.
I also doubt that anybody is using shared variables at all because I haven
Hi Blake,
these days GNU APL is following Dyalog APL because they are selling
their keyboards (and
I bought one). I just had forgotten to update the ]KEYBOARD command; the
config files shipped
with GNU APL should already reflect the Dyalog layout.
IBM seems to offer only APL keycaps, and Unic
Dear Juergen,
Thanks. If you are using the Dyalog standard then you should match my
(WASD custom) keyboard, so I'll be interested in the layout once you
correct ]KEYBOARD.
I am hoping you can included my WASD keyboard design and setup file with
GNU APL. This would make a high quality GNU APL ke
I agree with the suggestion to implement more extensions. There are a few
really interesting ones such as the power operator.
However, performance is something that needs to be worked on as well. Right
now there are cases where performance deteriorates very quickly, such as
when constructing and w
Interestingly, I think performance could be the real ticket to a large
resurgence of APL. The world has moved from faster processors to more
processors (and threads). APL is unique in its ability for the programmer
to express operations that can be parallelized. Ultimately, APL's ability
to tran
Well, there is a very specific case that is exposed when trying to build up
large arrays. That specific case has been discussed here a few times. It's
underlying cause is that GNU APL proactively copies the array it's working
on in case the user (i.e. the function that performs work on the data) of
On Sat, 2014-06-28 at 14:13 +0200, Juergen Sauermann wrote:
I also doubt that anybody is using shared variables at all because I
haven't received any trouble reports on them.
>
> /// Jürgen
>
That's true in my case.
Earlier this week I did make a first attempt to understand how SVs work.
In th
Should I add an extra feature to allow you to configure extra options for a
given session?
Regards,
Elias
On 29 June 2014 01:14, David B. Lamkins wrote:
> On Sat, 2014-06-28 at 14:13 +0200, Juergen Sauermann wrote:
> I also doubt that anybody is using shared variables at all because I
> haven'
Something like that would be helpful, yes.
What did you have in mind? A variant of the gnu-apl function that
prompts for options?
On Sun, 2014-06-29 at 01:18 +0800, Elias Mårtenson wrote:
> Should I add an extra feature to allow you to configure extra options
> for a given session?
>
>
> Regard
Perhaps a prefix command. It already allows you to prefix with a plain C-u
to specify apl binary. It could also ask for extra arguments.
Regards,
Elias
On 29 Jun 2014 01:31, "David B. Lamkins" wrote:
> Something like that would be helpful, yes.
>
> What did you have in mind? A variant of the gnu
That'd be great. Thanks.
On Sun, 2014-06-29 at 01:32 +0800, Elias Mårtenson wrote:
> Perhaps a prefix command. It already allows you to prefix with a plain
> C-u to specify apl binary. It could also ask for extra arguments.
>
> Regards,
> Elias
>
> On 29 Jun 2014 01:31, "David B. Lamkins" wr
I upgraded to SVN 346 and get the following on startup:
$ apl
execve() failed
::connect() to existing APserver failed: Connection refused
*** using local Svar_DB cache
after which the apl workspace is unresponsive unless I press ctrl-C,
then I get the message:
*** Failed to start APnnn: proce
apl.texi and the files derived from it refer to a command line option
"[no]COLOR," but in main.cc the options are "Color" and "noColor."
apl --noColor
works
apl --noCOLOR
yields "unknown option '--noCOLOR'"
15 matches
Mail list logo