Re: )LOAD WS bu no )COPY WS VAR

Hi Hans-Peter, works just fine on my machine: *   )CLEAR CLEAR WS   )COPY /tmp/BUGGY_CLOSE.xml NOTE: this workspaces was )SAVEd with syntax version 1.7.1 but is now )LOADed with a newer version 1.9.1. That should be OK, but new features introduced by the newer version will not be support

Re: Diamonds are ...

Hi Hans-Peter, this looks like a misunderstanding of how )COPY of )DUMPed files works. In the classical )SAVE/)COPY case the )COPY is atomic. In the )DUMP/)COPY case the )COPY is not atomic. In that case the )LOAD only starts the copy but does not finalize it. In fact the )COPY proceeds immedia

Re: Stacktrace )SAVEd Workspace

Hi Hans-Peter, the problem seems to be in the ravel of the value. Removing only the symbol (= APL variable) would leave the problem with the ravel in the .xml file. The proper way to fix the .xml is roughly: 1. remove the offending ... tag. 2. remove all references to the vid (value ID) of

Re: GNU APL Community Page Submissions

Hi ona... I have added the links, please check them: https://www.gnu.org/software/apl/Community.html It would also help if you could provide a shorter name for yourself. Best Regards, Jürgen On 2/26/25 02:28, ona-li-toki-e-jan-Epiphany-tawa-mi--- via Bugs and suggestions for GNU APL wrote:

Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

-Peter Am 05.03.25 um 16:57 schrieb Dr. Jürgen Sauermann: Hi Hans-Peter, I have added some optimizations to 10 ⎕CR. Please let me know if this helps. Best Regards, Jürgen On 2/26/25 20:07, Hans-Peter Sorge wrote: Hi Jürgen, thank you. Loading a )DUMPed  WS.apl  brings the variable back

Re: Stacktrace )SAVEd Workspace

Hi again, thanks, that helps. I will look into it. Best Regards, Jürgen On 3/3/25 00:26, Hans-Peter Sorge via Bugs and suggestions for GNU APL wrote: Hi, I nailed it down... The attached WS*BUG-HUNTER.xml *is in bug-condition. How to reproduce the bug (two sessions just for ease of analys

Re: Stacktrace )SAVEd Workspace

traces. after those 8 "corrections" the )LOAD was OK. I have included the Value and Ravel items. This type of bug persists with the workspace. I hope I can isolate the Variable to single out the cause. Best Regards Han

Re: A Question about zero rank disclose and a SYSTEM LIMIT in context.

┃a┃┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┃┗━┛┃ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ ┗ϵ━━┛ Looks like there are not more than 16 each Symbols allowed in such an expression:-) The oper

Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

ussed a problem with )SAVE when you suggested to use )DUMP. Having used )DUMP since then I was fine. Question: Is it 'save' to use )SAVE / )LOAD now? Best Regards Hans-Peter Am 26.02.25 um 15:48 schrieb Dr. Jürgen Sauermann: Hi Hans-Peter, thanks, fixed in *SVN 1843*. Best Rega

Re: A Question about zero rank disclose and a SYSTEM LIMIT in context.

Hi again, Hans-Peter, good news. I found and fixed the fault: *   E←⊂¨2 2⍴0/¨⊂,¨2 2 ⍴ 0⍴0   E≡⊃¨⊂¨E 1    E≡⊂¨⊃¨E 1 * *SVN 1847*. Best Regards, Jürgen On 3/1/25 16:35, Dr. Jürgen Sauermann wrote: Hi Hans-Peter, I cannot quite answer your question, but maybe we can find the

Re: (lack of) Monadic ≠ in GNU APL ('Nubsieve' / 'Unique Mask')

Added in *SVN 1846*. Best Regards, Jürgen On 2/22/25 03:50, Russtopia wrote: Through random wanderings watching videos on APL and J, I encountered a short segment on J's definition of the 'nub sieve' function (~:) https://aplwiki.com/wiki/Nub_Sieve In J (and, according to the "APL wiki" wh

Re: A Question about zero rank disclose and a SYSTEM LIMIT in context.

Hi Hans-Peter, I cannot quite answer your question, but maybe we can find the problem together. My analysis so far is this: I started with storing the common part of your c, d, and e in variable *E*. With that your examples become: *   E←⊂¨2 2⍴0/¨⊂,¨2 2 ⍴ 0⍴0   c←    E   d←  ⊃¨E    ⍝

Re: Missing gap line in output of multi dimentional array

Hi Hans-Peter, I am not sure if your observation below is an error. The relevant rule in the IBM APL2 language reference manual is this (Figure 22 on page 138): /* For Z←R, where R is a nested array:: ...  Z has LN intermediate blank lines between vertically adjacent items C and D, where: LN←0

Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

Hi again, forgot the second part. Yes, I believe using )SAVE and )LOAD is safe. Best Rgeards, Jürgen On 2/27/25 13:01, Dr. Jürgen Sauermann wrote: Hi Hans-Peter, there are ways to improve the )LOAD time. I did a complete rework of 10 ⎕CR, so I wanted to keep things simple in the beginning

Re: (lack of) Monadic ≠ in GNU APL ('Nubsieve' / 'Unique Mask')

Hi Russ, I will look into this. One observation so far is that your *Q←{ ((⍵⍳⍵)=⍳⍴⍵)/⍵ }* seems to return the unique elements rather than a boolean vector: *   Q←{ ((⍵⍳⍵)=⍳⍴⍵)/⍵ }   ⎕CR 'Q' λ←λ1 ⍵ λ← ((⍵⍳⍵)=⍳⍴⍵)/⍵   Q 'Hello, World' Helo, Wrd   ∪'Hello, World' Helo, Wrd* Look

Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

#x27;save' to use )SAVE / )LOAD now? Best Regards Hans-Peter Am 26.02.25 um 15:48 schrieb Dr. Jürgen Sauermann: Hi Hans-Peter, thanks, fixed in *SVN 1843*. Best Regards, Jürgen I have made a major re-disign of 10 ⎕CR B, hope it does not brake other On 2/16/25 12:35, Hans-Peter Sorge wro

Re: Stack trace when Tilde

Hi Hans-Peter, thanks, fixed in *SVN 1844*. Best Regards, Jürgen On 2/18/25 21:14, Hans-Peter Sorge wrote: *)clear* CLEAR WS * (⊂¨(1 0 1 0 0 1)   (1 1 1)) ⊂¨ ⊂¨(1 0 1 0 0 1) (1 1 1) * RANK ERROR  (⊂¨(1 0 1 0 0 1) (1 1 1))⊂¨⊂¨(1 0 1 0 0 1) (1 1 1)  ^  ^ */⍝ just

Re: During )dump / )copy, )dump / )load cycle the variable content gets lost and oone more stack trace.

Hi Hans-Peter, thanks, fixed in *SVN 1843*. Best Regards, Jürgen I have made a major re-disign of 10 ⎕CR B, hope it does not brake other On 2/16/25 12:35, Hans-Peter Sorge wrote: Hi, $ apl -q /⍝ create, rather simple, content/ * BUG←⊂⊂¨(1 2 0)⍴¨'X' */⍝ dump content/***  )dump buggy

Re: GNU APL Community Page Submissions

Hi,  thanks for sharing your workspaces. I am somewhat busy right now, so please remind me if I haven't updated the community page within 3 weeks. I am also wondering if we should have abstraction workspaces for ⎕FIO any longer. The one shipped with GNU APL is for backward compatibility only,

Re: Floating Point exception on cygwin64

Hi, I guess that running GNU APL in gdb might find the place where this occurs. Also: apl -l 37 to see how far the start-up comes. Unlike other logging levels -l 37 should work even if dynamic logging is  not configured. Best Regards, Jürgen On 2/23/25 19:00, Russtopia wrote: Hi all, has a

Re: Stack trace in fairly simple expression.

Hi Hans-Peter, thanks, fixed in *SVN 1842*. BTW: I am also working on your other issues, but it may take a little time. Best Regards, Jürgem On 2/18/25 17:01, Hans-Peter Sorge wrote: Hi, in SVN: 1833:1841M there is a stack trace for *x←, ⊂1 1 0 0 1 1**    y←,⊂'asdfgh'    

Re: Stop Vector Stack trace

Hi Hans-Peter, interesting side effect since I did not change anything in that area. Best Regards, Jürgen On 2/16/25 11:32, Hans-Peter Sorge wrote: Hi Jürgen, in SVN: 1833:1838M fixed too. Thank you and Best Regards Hans-Peter Am 14.02.25 um 17:20 schrieb Hans-Peter Sorge: Hi, $ apl -q

Re: Stack trace QuadCR space

Hi Hans-Peter, I believe that I have fixed the first Assertion below (even if I could not reproduce it on my box). *SVN 1838*. Many built-in functions return *0 0⍴0* because that is (the only ?) APL value that does not emit a \n when being printed (in many cases unintentionally). Also, several

Re: Syntax error on function )COPY'd from another workspace

Hi, latest news: I have corrected an error in the ∇-editor. *SVN 1833*. I am currently working on fixing a border case for function headers. Not entirely stable yet. Your problem might be related to specific function header cases. Best Regards, Jürgen On 2/10/25 13:55, Dr. Jürgen Sauermann

Re: Syntax error on function )COPY'd from another workspace

g this thread.  My impression is that it is not my code but a bug in GNU APL.  If it is my code, I am very happy to fix it.  I will take a look. Thanks. Blake On Sun, Feb 9, 2025 at 9:08 AM Dr. Jürgen Sauermann mailto:mail

Re: Syntax error on function )COPY'd from another workspace

chanisms. Only the ∇ editor gets me around the issue - ⎕FX ⎕CR 'function-name' does not. Any ideas on how I can help track this down? - Paul On Feb 8, 2025, at 11:34 AM, Dr. Jürgen Sauermann wrote: Hi Paul, that very much looks like an error in the Editor workspace, doesn't i

Re: Syntax error on function )COPY'd from another workspace

Hi Paul, that very much looks like an error in the Editor workspace, doesn't it? Can you reproduce the fault in plain APL? Best Regards, Jürgen On 2/6/25 19:14, Paul Rockwell wrote: I've been seeing syntax errors being thrown on functions copied from another workspace. I've imported Blake McB

Re: automatic )more and old-style multi line strings

Hi Roy, thanks, fixed in *SVN 1830*. As to a list of open issues: I am following a strategy of fixing all issues immediately and therefore there is no such list. Best Regards, Jürgen On 2/6/25 01:13, Roy Tobin wrote: Hi, Small polish needed. Seems that when automatic )more is on, a faulty/m

Re: Build errors of libapl on macos, Intel and ARM

Hi Mike, thanks, fixed in *SVN 1829*. Best Regards, Jürgen On 2/6/25 04:43, M.Hall wrote: Build errors of libapl on macos, Intel and ARM $ ./configure --with-libapl ... $ make ... /bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..    -Wall  -I sql -I /Volumes/ARCHIV

Re: Workspace XML file double quote problem

Hi Mike, I have fixed the double quote. *SVN 1828*. The NULs at the end of the document are on purpose. They guarantee that the document is 0-terminated after being *mmap*()'ed so that C string functions will not segfault when reaching the end of the *mmap()*'ed file.. The alternative would h

Re: Are lambdas different as the body of a direct function v. a ]usercmd?

Hi Roy, thanks, fixed in *SVN 1827*. Best Regards, Jürgen On 2/4/25 00:49, Roy Tobin wrote: (small bug with workaround, but not patch, follows) Hi, For a User-defined command defined with a lambda, I expect the omega is "the command entered by the user is passed to APL_fun as an APL string (

Re: Del Editor Confusion

Gentlemen, thanks, fixed in *SVN 1825*. Best Regards, Jürgen On 1/27/25 03:33, Paul Rockwell wrote: I'm seeing the same thing on SVN 1822 on Fedora 41 x86_64 and SVN 1823 on macOS 15.2 Apple Silicon (arm64). - Paul Rockwell On Jan 26, 2025, at 7:36 PM, M.Hall wrote: I have some misunder

Re: (low) cut-n-paste error in sample code for Quad FX interface

Hi Roy, thanks, fixed in *SVN 1824*. Best Regards, Jürgen On 1/28/25 07:27, Roy Tobin wrote: Possible cut-n-paste error on line 363 of src/native/template.hh? I presume the instrumenting literal should indicate that eval_fill_AB() was called.  I'm just going by inspection -- this observation

Re: Build fails against recent Clang/LLVM

Hi Alexey, thanks fixed in SVN *1823*. Best Regards, Jürgen On 1/22/25 20:01, Alexey Dokuchaev wrote: As of libc++19[1], std::char_traits<> is now only provided for char, char8_t, char16_t, char32_t, and wchar_t, and any instantiation for other types will fail. This breaks GNU APL on the Fre

Re: libgsl awkwardness

Hi Henrik, I believe the proper way to handle this is to use the VERSION argument in the *ax_path_lib_gsl.m4* script. Unfortunately your modified m4 script seems not to handle versions, and the original script https://www.gnu.org/software/autoconf-archive/ax_path_lib_gsl.html gives me a *4

Re: Quad-PW on macOS

y + // also wants ⎕PW to be controlled by the window size at start-up. + // We do this by by using the WINCH signal handler to pretend that + // there's a window size change + + signal_WINCH_handler(0);   // pretend window size change        }  #endif - paul On Dec 29, 2024, at 8:08 AM, Dr. Jürgen Sauermann wrote: Hi Paul, thanks, fixed in *SVN 1808*. Best Regards, Jürgen

Re: Quad-PW on macOS

st on macOS, hence the #include failure. Simply including is all that's needed to get the definition of the TIOCGWINSZ ioctl on macOS. I suspect that's the same on Linux as well. I'll test and report back. - paul On Dec 28, 2024, at 12:32 PM, Dr. Jürgen Sauermann wrote:

Re: Quad-PW on macOS

this infomration: static int get_win_size (int fd, struct winsize *win) {   int err = ioctl (fd, TIOCGWINSZ, (char *) win);   return err; } Regards, Elias On Wed, 25 Dec 2024 at 20:46, Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi Mike, I have applied your pat

Re: Quad-PW on macOS

.2). > Here's a patch; there's probably a better way to do it. On Mon, Dec 23, 2024 at 6:12 AM Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi, I am still not clear about whether the WINCH-SETS-⎕PW preference wo

Re: Quad-PW on macOS

Hi Kacper, thanks for reminding us of that option. The user can specify this behavior in one of her *preference* files (i.e.*$HOME/.config/gnu-apl.d/preferences* for one user;s preferences, or */etc/gnu-apl.de/preferences* for system-wide GNU APL preferences. The option is: ##

Re: Rev. 1997, make fails with Quad_MX.cc:

Makefile:5383: all-recursive] Error 1 make[2]: Leaving directory '/home/wheagy/git/apl/trunk/src' make[1]: *** [Makefile:546: all-recursive] Error 1 make[1]: Leaving directory '/home/wheagy/git/apl/trunk' make: *** [Makefile:434: all] Error 2 On 12/10/24 7:02 AM, Dr. Jürgen Sauer

Re: Rev. 1997, make fails with Quad_MX.cc:

before the #endif ? - Paul On Dec 10, 2024, at 10:45 AM, Hans-Peter Sorge wrote: Hi Jürgen. the bug persists. Best Regards Hans-Peter Am 10.12.24 um 13:02 schrieb Dr. Jürgen Sauermann: Hi Hans-Peter, Bill, as far as I can see the Apple error is bogus. However, I believe I found a solutio

Re: Rev. 1997, make fails with Quad_MX.cc:

x27; make: *** [Makefile:434: all] Error 2 On 12/10/24 7:02 AM, Dr. Jürgen Sauermann wrote: Hi Hans-Peter, Bill, as far as I can see the Apple error is bogus. However, I believe I found a solution in *SVN 1798*. Best Regards, Jürgen On 12/9/24 22:31, Hans-Peter Sorge wrote: Sorry - I get s

Re: Rev. 1997, make fails with Quad_MX.cc:

Hi Hans-Peter, Bill, as far as I can see the Apple error is bogus. However, I believe I found a solution in *SVN 1798*. Best Regards, Jürgen On 12/9/24 22:31, Hans-Peter Sorge wrote: Sorry - I get some horrible big letters in my original post. High-res and font settings and manual adjust and

Re: Compile error, "OP_UNKNOWN", debian

Hi Bill, thanks, fixed in *SVN 1795*.. Best Regards, Jürgen On 12/7/24 22:01, Bill Heagy wrote: after make clean; ./configure;make -j2 .. g++ -DHAVE_CONFIG_H -I. -I..    -Wall -Wno-parentheses -I sql -I /home/wheagy/git/apl/trunk  -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/

Re: 4 errors generated when compiling Quad_MX,hh

Hi. thanks. Hopefully fixed in *SVN 1789*. On 12/2/24 22:21, Paul Rockwell wrote: I agree with you Henrik that’ it’s Jürgen’s call here on what would be the best way forward. I suspect you and Jürgen didn’t encounter the issue because you’re using a GCC compiler suite that defaults to a newe

Re: Matrix native function

Hi Henrik, thanks a lot for contributing ⎕MX. It is now included in *SVN 1786*. I made a few changes to adapt it to the GNU APL coding style. Please double-check if everything went OK. I noticed a minor difference in the *Quad_MX.tc* testcase file on my machine, probably caused by rounding err

Re: Matrix native function

'll port mtx as a ⎕MX extension and send you a patch. Thanks, great. Expect some rework on my side. Henrik On 11/2/24 08:14, Dr. Jürgen Sauermann wrote: Hi Hendrik, I am wondering if it may make sense to make those functions built-ins? As of today only QR-factorization is built-in but I a

Re: Matrix native function

Hi Hendrik, I am wondering if it may make sense to make those functions built-ins? As of today only QR-factorization is built-in but I always felt that that may be too little (at least if compared to packages like e.g. LApack), with f being a function selector or a function name like in ⎕FX and

Re: APL lambda question

anyone but me is using mtx, so it's cool if LAZY isn't in your plans--it just means I patch the line when you put out a new SVN. Thanks, Henrik On 10/24/24 11:30, Dr. Jürgen Sauermann wrote: Hi Henrik, I believe I fixed the Segfault. You should now get a DEFN ERROR instead with )MO

Re: APL lambda question

Probably not worth trying to fix this--it's too obscure. [3] ~tinkering/apl/mtx/src > On 10/23/24 12:30, Dr. Jürgen Sauermann wrote: Hi Hendrik, as far as I remember: in GNU APL a lambda is pretty much a regular defined function. A nomadic lambda is simply a dyadic lambda which te

Re: APL lambda question

Hi Hendrik, as far as I remember: in GNU APL a lambda is pretty much a regular defined function. A nomadic lambda is simply a dyadic lambda which test for the presence for its left argument (read: ⎕NC lambda = 2).Tour tryit needs to check that before ⍺ is referenced). Best Regards, Jürgen

Re: I get ompile errors in 1788

Hi, thanks, fixed in *SVN 1781*. Best Regards, Jürgen On 9/27/24 05:40, Paul Rockwell wrote: Peter, I've seen these warnings in Quad_PNG.cc - they appear to be harmless. I've re-written the definitions of both PNG_GTK and PNG_LIBS so that they are no longer flagged by the compiler as poten

Re: multiple assignment

Hi, thanks. Hopefullt fixed in *SVN 1780.* Pl ease complain if not. Best Regardsm Jürgen On 9/22/24 17:27, Ala'a Mohammad wrote: I'd cloned the svn repository and tried to compile it but got the following: Quad_PNG.cc:923:1: error: redefinition of ‘Token Quad_PNG::eval_AB(Value_P, Value_P) co

Re: GNU APL 1.9 Released

Jul 2024 13:12:47 +0200 Dr. Jürgen Sauermann wrote: That is correct. A GNU APL release is the state of the software at a point in time where it is stable. Stable means that all major trouble reports are fixed and no new functionality is planned or in progress. It is also a synchronization point

Re: GNU APL 1.9 Released

is only a small part of what the apl --cfg outputs and takes up valuable screen space when trying to work on different compiles the apl -v should show what the configure options are like gcc -v does On Wed, 3 Jul 2024 12:28:59 +0200 Dr. Jürgen Sauermann wrote: Hi, *apl -v* should be short.

Re: GNU APL 1.9 Released

oblem. On 7/9/24 19:47, enz...@gmx.com wrote: Jurgen why do you always evade answering significant problems? On Mon, 1 Jul 2024 12:08:50 +0200 Dr. Jürgen Sauermann wrote: Hi, yes it is a snapshot of the current SVN. No need to do anything if you update via SVN. Best Regards, Jürgen On 6/

Re: GNU APL 1.9 Released

release has ended. That implies that trouble reports on older releases will not be accepted unless the problem reported still exists in the latest release. On 7/3/24 23:36, enz...@gmx.com wrote: so it is really 2 weeks stable release? On Mon, 1 Jul 2024 12:08:50 +0200dp Dr. Jürgen Sauermann

Re: GNU APL 1.9 Released

good as apl itself there was a guy here within the last year who had problems with libapl that were never resolved On Mon, 1 Jul 2024 12:08:50 +0200 Dr. Jürgen Sauermann wrote: Hi, yes it is a snapshot of the current SVN. No need to do anything if you update via SVN. Best Regards, Jürgen On

Re: GNU APL 1.9 Released

apl_missing_headers is referring to in addition to the number On Mon, 1 Jul 2024 12:08:50 +0200 Dr. Jürgen Sauermann wrote: Hi, yes it is a snapshot of the current SVN. No need to do anything if you update via SVN. Best Regards, Jürgen On 6/30/24 18:55, enz...@gmx.com wrote: Hi, is this apl-1.9.tar.gz

GNU APL 1.9 Released

Hi, I am happy to announce that *GNU APL 1.9* has been released. GNU APL is a free implementation of the ISO standard 13751 aka. "Programming Language APL, Extended". The 1.9 release contains: * Bug fixes Have fun! Dr. Jürgen Sauermann Author and Maintainer of GNU APL P.S. Some

Re: Questions regarding current GNU APL versions and source availability

Hi Russ, see below. Best Regards, Jürgen On 6/28/24 05:46, Russtopia wrote: Hi, I have a few questions about the versioning and distribution of GNU APL as it stands today: 1. Versioning GNU APL is apparently still officially '1.8'. Even after many, many bug fixes and enhancements, since th

Re: Matrix ops native functions

Hi Henrik, thanks a lot for sharing your code! Best regards, Jürgen On 5/15/24 01:09, Henrik Moller wrote: I do a lot of stuff with matrices and it occurred to me a couple of days ago to start packaging some of them as gnu APL native functions I don't think are built into the present release.

Re: Source directory with space in name causes configure failures

Hi Mike, thanks for reporting this. Spaces in filenames are these days supported on most platforms but discouraged due to their bad interactions with shells. Fixing this would require fixing it in autoconf which is used by GNU APL, but not provided by it. I would rather recommend to name your

Re: General chatter.

Hi Chris, some experience of mine that might help. 1. Some time ago I tried really hard to compile GNU APL with the (standard?) Microsoft C++ compiler so that GNU APL runs natively under Windows. I don't remember which compiler (there seems to be a few of them), but I got thousands of errors a

Re: Multiple assignment attempt crashes gnu-apl

Hi Mike, first of all the statement is correct: *  (a b c) ← 5   a 5   b 5   c 5 * Could you please check if the error also occurs in a freshly started interpreter (as to rule out that something might have been wrong with one of the variables *a*, *b*, or *c*? If would also h

Re: Error buildin APL on Linux

kup/apl/src' make[2]: *** [Makefile:5340: all-recursive] Error 1 make[2]: Leaving directory '/home/blake/Backup/apl/src' make[1]: *** [Makefile:542: all-recursive] Error 1 make[1]: Leaving directory '/home/blake/Backup/apl' On Thu, Mar 14, 2024 at 8:46 AM Dr. Jürgen Sau

Re: Error buildin APL on Linux

Hi Blake, thanks, fixed in *SVN 1765*. Best Regards, Jürgen On 3/10/24 17:58, Blake McBride wrote: Greetings, I am getting the following error building GNU APL on a Fedora Linux box: [...]  /usr/bin/mkdir -p '/usr/local/share/doc/apl'  /usr/bin/install -c -m 644 SQL.apl '/usr/local/share/do

Re: Error message references wrong line

Hi Hans-Peter, thanks, fixed in *SVN 1764*. Best Regards, Jürgen On 3/6/24 15:24, Hans-Peter Sorge wrote: Hi, Just for fun i did some "Home work" for my wife. Kids in  school were to guess (and calculate) numbers. For the calculation part I came up with an APL Funktion (No more school - rig

Re: Compile errors when building libapl

Hi Mike, Paul thanks, *libapl* should compile now (*SVN 1761*). Please check that the libapl function *get_function_ucs()* still works. Best Regards, Jürgen Sauermann On 3/3/24 21:36, Paul Rockwell wrote: I've done a little digging into the source code. I hope this helps. libapl.cc hasn't be

Re: Double DUMPED message

Hi Blake, could it be that your workspace YYY )LOADs or )COPYs another workspace? If so then each workspace prints its DUMPED message. Best Regards, Jürgen On 2/26/24 00:44, Blake McBride wrote: See the following log:       )load YYY DUMPED 2023-01-16  09:39:01 (GMT-5) DUMPED 2024-02-25  18:

Re: Is svn release 1758 missing fixes?

Hi Mike, sorry for that, it came after *#ifdef APPLE* so I did not notice it. I am not a MAC owner, so I can't compile myself but rather depend on your reports. Now hopefully fixed in *SVN 1760*. As to svn, you simply check out GNU APL once (as you did) and then *svn up* to fetch that changes

Re: Is svn release 1758 missing fixes?

Hi Paul, thanks, fixed in *SVN 1759 *as proposed. I was initially thinking of *return st.st_mtime;* myself but didn't do it because is is a macro and I wasn't sure if it is #define'd on all platform. Best Regards, Jürgen On 3/4/24 02:49, Paul Rockwell wrote: Mike, I noticed the same issu

Re: GNU APL crash

Hi Paul, thank you for reporting this issue. Fixed in *SVN 1757*. Best Regards, Jürgen On 2/22/24 19:04, Paul Rockwell wrote: Environment: SVN 1754, macOS 14.3.1, M1 Mac mini (Apple Silicon) While attempting to run Blake McBride's APL Editor https://github.com/blakemcbride/APLEditor I encou

Re: SVN 1752: error in Command.cc doesn't compile on macOS

iPhone On Feb 14, 2024, at 3:43 AM, Dr. Jürgen Sauermann wrote:  Hi Paul, thanks. Could you please have a look at your*/usr/include/.../stat.h* file and let me know how to get the modification time (or a macro that tells if it is present or absent)? Thanks, Jürgen On 2/13/24 19:56, Paul

Re: SVN 1752: error in Command.cc doesn't compile on macOS

Hi Paul, thanks. Could you please have a look at your*/usr/include/.../stat.h* file and let me know how to get the modification time (or a macro that tells if it is present or absent)? Thanks, Jürgen On 2/13/24 19:56, Paul Rockwell wrote: When compiling SVN 1752 on macOS, an error is thrown b

Re: Stack traces not displaying correctly on macOS

Hi Paul, thanks. I have incorporated your diffs, *SVN 1752*. Please check on your Apple since I don't own one (*⎕FIO ¯16* to provoke a stack dump). I was also wondering where macro *_APPLE_* is defined. In a header file (which ?) or with -D on the command line? In the latter case we could let ./

Re: Error while running function copied from another workspace

Hi Paul, thanks, fixed in *SVN 1746*. BTW, GNU APL has as number of *⎕CR *sub-functions which do pretty much the same as (or occasionally nicer than) the DISPLAY workspace from IBM APL2. E.g. *   2 ⎕CR ⊂1 2 3 .→. |1 2 3| '-'   3 ⎕CR ⊂1 2 3 ┏→┓ ┃1 2 3┃ ┗━┛ * See *⎕CR ⍬* fo

Re: Should GNU APL write to .apl.history when invoked with the --eval option?

Hi, IMHO it would be somewhat odd if the history were dependent on command line options. Instead you can set the file where the history is written in one of the the preferences files. The default is .apl.history (i.e. in the current directory). If you need multiple places for the history unde

Re: Segmentation fault

Hi Mike, thanks for reporting this. Fixed in *SVN 1745*. Best Regards, Jürgen On 2/1/24 19:04, M.Hall wrote: On macos Mojave 10.15.7 x64, gnu-apl built from svn sources, apl installed into /usr/local/bin, input "[]" gives segmentation fault.  Did I build it wrong? >> $ uname -a Darwin

Re: GNU APL error while saving workspace

  Welcome to GNU APL version 1.8 / SVN: 1740M                  Copyright © 2008-2023 Dr. Jürgen Sauermann                        Banner by FIGlet: www.figlet.org                 This program comes with ABSOLUTELY N

Re: Test adn debug bug

Hi Bill, seems like opening your database fails: *   sqlh←ctrgl_sql_connect 'localhost' 'dalyw' 'ctrgl_revised' '1BBmXEc0' DOMAIN ERROR+ SQL∆Connect[19]  Z←type ⎕SQL[1]arg    ^   ^* It also looks like there is some *)MORE* information available which provides some more

Re: Getting started with APL

prompt answer. I will have a look at those. Is "Mastering Dyalog APL" compatible with GNU APL? I was affraid that I would have trouble with this book if there are example code which only works with Dyalog. Thanks. G. Dindi On Tue 19-Dec-2023 at 11:50:33 +01, Dr. Jürgen Sauermann wrote:

Re: Getting started with APL

Hi Gariola, I believe that the simplest way of learning APL is by examples. There are many good books around, for example Dyalogs "Mastering Dyalog APL": https://www.dyalog.com/uploads/documents/MasteringDyalogAPL.pdf I personnaiiy like"APL ― An Interactive Approach" by Gilman and Allen (not su

Re: Quad-gtk

Hi Bill, I had a log at your build logs and they look OK. How about the questions below? I have checked ⎕GTK and it is nowhere near to throwing a SYNTAX ERROR. So for me it is important to know where the syntax error is thrown. Best Regards, Jürgen On 11/12/23 15:44, Dr. Jürgen Sauermann

Re: Quad-gtk

Hi, sorry to hear that. Works just fine on my box. But we may be able to narrow down the problem a litte. Please try the following: 1. make sure that the Gtk_server was installed and is executable: * $> Gtk_server -v Gtk_server: fcntl(3, F_GETFD) failed: Bad file descriptor     That typically ha

Re: GTK

Hi Bill, thanks for reporting this. And congratulations for probably being the second *⎕GTK *user (I am judging the popularity of system functions like *⎕GTK* by the number of trouble reports that I receive). The problem you see is most likely caused by a missing ID in the top-level window. It

Re: macOS warning present in build 1735

f test CXX = "$tagname"; then  case ${MACOSX_DEPLOYMENT_TARGET-10.0} in  10.[0123])  func_append compile_command " $wl-bind_at_load"  func_append finalize_command " $wl-bind_at_load"    ;;  esac Could that be the culprit? On Oct 3, 2023, at 09:18, Dr. Jürgen Sauermann

Re: macOS warning present in build 1735

Hi Louis, thanks for reporting this. I believe that I managed to fix all compiler warnings. The linker warning: *ld: warning: -bind_at_load is deprecated on macOS* seems to be caused by different libtool versions. Maybe running *libtoolize* on your box in the top-level GNU APL directory fixe

Re: [EXTERNAL]Building GNU APL with clang

Hi, thank you all for discussing this. To address at least some of the issues i have: 1, removed typeof() entirely, and 2. replaced *std::auto_ptr<>* with *std::unique_ptr<>*   as proposed on the internet. I am not entirely sure about 2. though. It was only used twice in  emacs_mode and once i

Re: libpq.so.5: no version information available

Hi Blake, thank you for reporting this. It very much looks like this message is generated inside the libpq library, probably in the initialization of the library. Not much that I can do about it. I also checked my libpq (mine is libpq.so.5.14) and that one seems not to contain anything near to t

Re: )LOAD dumped WS had a name clash - ⎕FC affects )DUMP

from that time. And no - that is not Corona. How the E-13 got into a *newly* created WS (one week old) is  out of my scope. And the )load only failed because i have a function E on board. Within my apl / xml inventory there is no  E¯13 / e-13 mix. Best Regards Hans-Peter Am 29.09.23 um

Re: )LOAD dumped WS had a name clash - intermittend

Hi Peter, it very much looks like the VALENCE ERROR is caused by the minus sign in 1E-13. The question is where the minus comes from. There are two possibilities: 1. The most likely case is that the user has written 1E-13 in some    APL script (but meant to write 1E¯13). In this case GNU APL see

Re: Execute on empty element produces a stack trace

Hi Peter, thanks, fixed in *SVN 1734*. Best Regards, Jürgen On 9/27/23 23:08, Hans-Peter Sorge wrote: Hi, *This gives a stack trace:*     X←0 2⍴ ⊂'0'     ⍎¨X[;1] == Assertion failed: start <= body_fr

Re: output formatting

Hi Stephen, On 9/10/23 21:58, Stephen Lewis via Bugs and suggestions for GNU APL wrote: ... When using 'apl' script in a pipeline I was surprised to find formatting clearly designed for a terminal when output was going to a file. Especially when the formatting has the effect of changing the shap

Re: output formatting

Hi, the problem seems to be that you let APL print to a terminal (which wraps long lines at ⎕PW). A better way is probably to use one of the ⎕FIO functions in your APL script as to write directly to the output file (which bypasses the terminal). Of course output forwarding in the shell would no

Re: AES in GNU APL

Hi Robin, thanks a lot for sharing it. Have a nice weekend, Jürgen On 8/28/23 04:57, Robin Haberkorn wrote: Hello everyone! Here's a complete implementation of AES in GNU APL, that I thought might be worth sharing: https://gist.github.com/rhaberkorn/78a982dbd49bc896175607289507cb64 It's pu

Re: Prefix.cc message

Hi Bill, thanks. I have removed the message (a debug left-over). *SVN 1725*. Best Regards, Jürgen On 8/12/23 17:09, Bill Daly wrote: I'm sending a log including the final message: fifo[si=0 len=4 PC=4] is now : TC_END TC_SYMBOL TC_ASSIGN TC_VOID at Prefix.cc:529 I generated this by loadin

Re: apl won't start 2

Hi Bill, thanks, fixed in *SVN 1724*. Best Regards, Jürgen On 8/10/23 16:20, Bill Daly wrote: It seems related to this CONTINUE workspace.  When I moved it out of workspaces, I got the 6 space prompt. w

Re: Link errors with latest GNU APL on Linux Devuan Chimaera (stable)

in my installation environment. Thanks, -Russ On Tue, Jul 4, 2023 at 5:00 AM Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi Russtopia, thank you for reporting this. Seems like I incorrectly assumed that the presence of libxcb implied the

  1   2   3   4   5   6   7   >