Re: [Bug-apl] Package metadata format

Hi Elias, I believe so. For my taste there are to many [axes] which should be*⎕IO+'*ed to be portable. How about this instead: * { ⊃1**↓**,((⊂⍺)≡¨ ,0 ¯1↓⍵)⌿⍵ }* /// Jürgen On 08/03/2014 05:55 PM, Elias Mårtenson wrote: I wrote this function to print the value(s) of a given field:

[Bug-apl] gnu-apl-mode C-c C-h

Elias, would you be willing to accept a patch to configure the comment prefix in gnu-apl--find-documentation-for-defined-function? (I prefer ⍝ over ⍝⍝.) -- "The secret to creativity is knowing how to hide your sources." Albert Einstein http://soundcloud.com/davidlamkins http://reverbnation.c

Re: [Bug-apl] ERR function in APL2?

Hi Elias, ERR is indeed a function, defined on page 49 of that document. /// Jürgen On 08/04/2014 08:13 AM, Elias Mårtenson wrote: I was browsing the APL2 documentation, and came across the following code (page 56, on the PDF here ):

Re: [Bug-apl] Another build error on OSX

Hi Elias, I have changed ./configure to check this. SVN 415. /// Jürgen On 08/03/2014 06:01 PM, Elias Mårtenson wrote: Apple is allergic to GPLv3, and I believe that they are shipping a stone-age version of it, just like they do for Emacs. If these features are required, then I suggest chec

Re: [Bug-apl] Can't break out of the middle on a display operation

Hi Elias, I have changed the max. interval from 500ms to 1 second. SVN 415. I believe changing to single ^C via configuration would be more confusing than helpful because the behavior under emacs (i.e. INTERRUPT = ATTENTION) would deviate from the behavior outside emacs (INTERRUPT ≠ ATTENTION)

[Bug-apl] build warning on OSX

I did a brand new SVN co and then did ./configure and got this warning file://localhost/Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/workspaces/SCRIPT.apl: warning: Missing file: /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/workspaces/SCRIPT.apl is missing from working copy. Pete

[Bug-apl] gnu-apl-mode, Unix domain socket, and process buffer?

Elias, When running gnu-apl-mode with a Unix domain socket for connection to libemacs, does there really need to be a buffer (*gnu-apl-connection*) for the process? There isn't a buffer if the connection is via TCP. -- "The secret to creativity is knowing how to hide your sources." Albert Ein

Re: [Bug-apl] Can't break out of the middle on a display operation

Thank you. I think this will work better. Regards, Elias On 5 Aug 2014 01:50, "Juergen Sauermann" wrote: > Hi Elias, > > I have changed the max. interval from 500ms to 1 second. SVN 415. > > I believe changing to single ^C via configuration would be more confusing > than helpful because the beh

[Bug-apl] Useful range of decode function is limited.

Juergen, Please consider the following: ( 62 ⍴ 2 ) ⊤ ⎕ ← 2 ⊥ 53 ⍴ 1 9007199254740991 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 ( 62 ⍴ 2 ) ⊤ ⎕ ← 2 ⊥ 54 ⍴ 1 18014398509481984 0 0 0 0 0 0 0 1

Re: [Bug-apl] Useful range of decode function is limited.

Mathematically, the term "small" is ambiguous. Perhaps that's why Common Lisp names its corresponding value MOST-NEGATIVE-FIXNUM. That said, in GNU APL, these numbers are somewhat bogus anyway. In particular, the *actual* maximum number that can be stored without loss of precision depends on the u

Re: [Bug-apl] gnu-apl-mode, Unix domain socket, and process buffer?

Of course. I'm using make-network-process to open the Unix Domain socket connection, and I had just casually passed in the name of a buffer, thinking that it was required. Of course it isn't (as I figured out reading the documentation a bit more), so I've fixed it. Thanks. Regards, Elias On 5 A

Re: [Bug-apl] gnu-apl-mode, Unix domain socket, and process buffer?

Only reason I noticed it is because the extra buffer interfered with tab-completion for *gnu-apl*... Thanks! On Mon, Aug 4, 2014 at 8:41 PM, Elias Mårtenson wrote: > Of course. I'm using make-network-process to open the Unix Domain socket > connection, and I had just casually passed in the na

Re: [Bug-apl] gnu-apl-mode, Unix domain socket, and process buffer?

Just bind a key to the function gnu-apl. If there is already a session open, it will switch to that one. :-) Regards, Elias On 5 August 2014 12:26, David Lamkins wrote: > Only reason I noticed it is because the extra buffer interfered with > tab-completion for *gnu-apl*... > > > Thanks! > > >

Re: [Bug-apl] gnu-apl-mode C-c C-h

Actually, not really. The choice of prefix character has been discussed in a few separate threads here, and we finally seems to have settled on the use of two lamps at the beginning for the function to indicate Doxygen documentation. If you want to use a different style for your own code, I'd sugg

[Bug-apl] VAX APL at Bitsavers

I was casually browsing the Bitsavers archive and I came across these two manuals for VAX APL. There is some interesting information in there, especially relating to how a user session was conducted in 1991 using the DEVwindows client. https://archive.org/details/bitsavers_decvaxlangsersGuideJun91

Re: [Bug-apl] ERR function in APL2?

Thank you. I see now how it works. Personally, I'd use Quad-ES to set an error state instead. Was Quad-ES available on APL2? Regards, Elias On 5 August 2014 01:42, Juergen Sauermann wrote: > Hi Elias, > > ERR is indeed a function, defined on page 49 of that document. > > /// Jürgen > > > > On

Re: [Bug-apl] Useful range of decode function is limited.

Hello Elias, 1) "MOST-NEGATIVE-FIXNUM" and "largest negative integer" are much closer in connotation to each other than either is to "smallest (negative) integer". "smallest" and "largest" are generally used when comparing the magnitudes (or absolute values) of numbers irrespective of the signs o

Re: [Bug-apl] gnu-apl-mode C-c C-h

OK. No worries. That's why I asked first. :) On Mon, Aug 4, 2014 at 9:30 PM, Elias Mårtenson wrote: > Actually, not really. The choice of prefix character has been discussed in > a few separate threads here, and we finally seems to have settled on the > use of two lamps at the beginning for the

Re: [Bug-apl] Useful range of decode function is limited.

Your observations are all correct. The behaviour you see are because GNU APL values can be either integers (backed by a 64-bit integral value) or floating point (backed by a C++ double value). Conversions between these two underlying storage formats are transparent to the user most of the time. *I