Hi Blake,
I am really sorry to hear that. I am also coming from the old APL times
where empty values were just that - empty.
It took a while to grasp how APL2 handles empty values and as we have
seen the implementation of empty values
in GNU APL is not always correct. So I hope that your frus
Hi Jay,
thanks, fixed in SVN 262.
/// Jürgen
On 05/12/2014 06:26 PM, Juergen Sauermann wrote:
Hi,
looks like a bug, I will look into it.
/// Jürgen
On 05/12/2014 05:28 PM, Jay Foad wrote:
⍬≡⊃⊂⍬
0
That looks like a bug in GNU APL. It's true in IBM APL2 and Dyalog APL.
Jay.
Hi Elias,
thanks, fixed in SVN 263.
/// Jürgen
On 05/12/2014 05:23 PM, Elias Mårtenson wrote:
I noticed that my error messages were not coloured anymore, and I
discovered that the special control sequences were not sent anymore.
The solution is to set use_curses to false where the special s
Hi Akiva,
could not reproduce it with ^C but with ^D (which normally means
end-of-input).
Instead of throwing a segfault we will no )OFF after the 5'th ^D (to
avoid )OFF when
hitting ^D accidentally. SVN 264.
Thanks,
/// Jürgen
On 05/11/2014 03:29 AM, Akiva Avraham wrote:
I don't know if yo
Hi Elias,
wouldn't it then be easier for the user to load the emacs lib when
--emacs is given?
BTW we could make --emacs an entry in the preferences file so that the
user does not
need to give it on the command line every time.
/// Jürgen
On 05/11/2014 03:12 AM, Elias Mårtenson wrote:
Ind
Hi Chris,
thank you!
/// Jürgen
On 05/03/2014 07:15 AM, Chris Jones wrote:
I finally wrote a GNU/apl XCompose file that can provide a quick, no
headaches :) alternative to more orthodox methods such as xmodmap or
setxkbmap + a third-level modifier.
This hack may come in handy for new users o
Hi,
I guess I know what went wrong. The workload per thread was so small
(reading the CPU cycle counter and that was it) that the first threads will
have finished while the tasks were still being distributed.
Due to the lack of core binding, some cores would therefore be used several
times and c
It would be nice if:
∇myfun[⎕]∇
would list the function in the main window (the one with the above
statement) rather than give an error. Sometimes it is nice to just list
the definition.
Thanks.
Blake
You can use monadic ⎕CR for that. When passed the name of a function, it
will return the content of said function.
Regards,
Elias
On 13 May 2014 20:43, Blake McBride wrote:
> It would be nice if:
>
>∇myfun[⎕]∇
>
> would list the function in the main window (the one with the above
> sta
>From the Emacs mode's perspective, that would be perfectly appropriate of
course. However, the native library module is, despite its name, not
necessarily specific to Emacs. It implements a generic protocol that any
external tool could use. It's not guaranteed that a user of the native
module want
Greetings,
Not understanding enclose/disclose, I am not sure if this is correct
behavior or not. Basicilly, with ]boxing turned on, the following code
produces some sort of data item that I cannot re-produce without the pair.
Turn on ]boxing and try:
⊃⊂''
or
⊃⊂0⍴0
They produce something that
Yes, that's the bug that was mentioned earlier. The result should be the
same as ''. Jürgen confirmed this bug, so I'd expect it to be fixed soon.
:-)
Regards,
Elias
On 13 May 2014 21:14, Blake McBride wrote:
> Greetings,
>
> Not understanding enclose/disclose, I am not sure if this is correct
Okay, thanks. I am writing the box/unbox that I spoke of and it depends on
what gets returned in my reported case. I can make it work either way, but
it would change based on what is actually returned. Since this behavior is
in flux, I may wait.
Thanks!
Blake
On Tue, May 13, 2014 at 8:16 AM
Hi,
I thought I did in SVN 262?
/// Jürgen
On 05/13/2014 03:16 PM, Elias Mårtenson wrote:
Yes, that's the bug that was mentioned earlier. The result should be
the same as ''. Jürgen confirmed this bug, so I'd expect it to be
fixed soon. :-)
Regards,
Elias
On 13 May 2014 21:14, Blake McBr
You most certainly did. I just updated and now it's fixed. Thanks for that.
:-)
Regards,
Elias
On 13 May 2014 21:48, Juergen Sauermann wrote:
> Hi,
>
> I thought I did in SVN 262?
>
> /// Jürgen
>
>
>
> On 05/13/2014 03:16 PM, Elias Mårtenson wrote:
>
> Yes, that's the bug that was mentioned e
Yes indeed. I rebuilt and it works as expected now. Thanks!
Blake
*Blake McBride*
www.arahant.com
Cell:615-394-6760
Office: 615-376-5500
Fax: 615-377-6006
On Tue, May 13, 2014 at 8:49 AM, Elias Mårtenson wrote:
> You most certainly did. I just updated and now it's fixed. Thanks
I wrote two APL functions that operate like ⊃ and ⊂ packing an APL1 array
into a scalar and unpacking it back into its APL1 array. It works as
Iverson preferred, and is simple to understand and use. There are no
exceptions to what can be nested (i.e. scalars can be recursively nested).
And there
In GNU APL, when you list a function via:
∇fun[⎕]∇
the format of the returned output has several problems (inconsistencies
with respect to the IBM documentation). Some of the differences are small
but it would be nice of they were corrected. One difference is important
in my opinion. I will us
SVN Revision: 264
{⍵}¨''
SEGMENTATION FAULT
-- Stack trace at main.cc:122
0x7f97fe168d65 __libc_start_main
0x43557d main
0x52627d Workspace::immediat
19 matches
Mail list logo
