Segmentation fault

2024-02-01 Thread M.Hall
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 mbp13 19.6.0 Darwin Kernel Version 19.6.0: Tue Jun 21 21:18:39 PDT 2022; root:xnu-6153.141.66~1/RELEASE_X86_64 x86_64

Compile errors when building libapl

2024-03-02 Thread M.Hall
Summary, two errors: libapl.cc:571:39: error: too few arguments to function call, expected 2, have 1 sym->resolve_right(tos[j]); ./Symbol.hh:217:4: note: 'resolve_right' declared here virtual void resolve_right(Token & token, Function_PC & PC) const; libapl.cc:

Is svn release 1758 missing fixes?

2024-03-03 Thread M.Hall
Is svn release 1758 missing fixes for Backtrace.cc and Command.cc ? On macos 10.15.7 (old, I know). I added small fixes in my "working copy" below to avoid compile errors - the diff will show them. (Also, '__APPLE__' is defined by the compiler. See the output of 'echo | g++ -dM -E -' as in the lib

Multiple assignment attempt crashes gnu-apl

2024-03-27 Thread M.Hall
I saw a multiple assignment statement in the book "Learning APL with APLX", and tried it, not knowing if GNU-APL accepted it or not. I expected maybe a syntax error, but instead it crashes with a backtrace. I know 'a←b←c←5' works, but I was just playing around with a statement I hadn't seen before.

Re: General chatter.

2024-03-29 Thread M.Hall
Perhaps Dyalog? https://www.dyalog.com/dyalog/microsoft-windows.htm https://www.dyalog.com/dyalog/current-platforms.htm On Fri, Mar 29, 2024 at 12:47 PM Chris Moller wrote: > First, due to my old ISP having apparently gone out of business while > keeping my mollerware.com domain locked, my

Source directory with space in name causes configure failures

2024-05-02 Thread M.Hall
Project:GNU APL Version / SVN: 1.8 / SVN: 1775M Build Date: 2024-04-24 13:04:25 UTC Build OS: Darwin 23.3.0 arm64 config.status: default ./configure options Archive SVN:1775 When the source directory path has a space in it, the configure script fails

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

2025-02-10 Thread M.Hall
$ apl )clear CLEAR WS →(0=⍴0)/0 SYNTAX ERROR+ →(0=⍴0)/0 ^ )more branch back into function (→N) without suspended function Running SVN 1833. On Mon, Feb 10, 2025 at 10:01 AM Hans-Peter Sorge < hanspeterso...@netscape.net> wrote: > Sorry - > > an even shorter way . >

Warning messages, MacOS M3 clang, SVN 1832 and 1833.

2025-02-10 Thread M.Hall
Warning messages, MacOS M3 clang, SVN 1832 and 1833. It might be because things are changing right now. === ... g++ -DHAVE_CONFIG_H -I. -I..-Wall -I sql -I /Volumes/ARCHIVE/Language/APL/gnu-apl/SVN -g -O2 -I /Volumes/ARCHIVE/Language/APL/gnu-apl/SVN -MT apl-TabExpansion.o -MD -MP -MF

Build errors of libapl on macos, Intel and ARM

2025-02-05 Thread M.Hall
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/ARCHIVE/Language/APL/gnu-apl/SVN -g -O2 -I /Volumes/ARCHIVE/Language/APL/gnu-apl/SVN -MT libap

Re: Workspace XML file double quote problem

2025-02-02 Thread M.Hall
Found it. Looks like XML_Saving_Archive::emit_token_val() line 769 of src/Archive.cc was adding its own close quote. $ diff -u src/Archive.cc-ORIG src/Archive.cc --- src/Archive.cc-ORIG 2025-02-02 15:07:35.0 -0600 +++ src/Archive.cc 2025-02-02 15:07:24.0 -0600 @@ -766,7 +766,7 @@

Re: Workspace XML file double quote problem

2025-02-02 Thread M.Hall
Never mind. It does break other things. I should leave the programming to the professionals. Sorry. On Sun, Feb 2, 2025 at 8:27 PM M.Hall wrote: > Found it. > Looks like XML_Saving_Archive::emit_token_val() line 769 of src/Archive.cc > was adding its own close quote. > >

Workspace XML file double quote problem

2025-01-31 Thread M.Hall
I saved a workspace and ran 'xmllint' on it: $ xmllint c01-sets.xml c01-sets.xml:640: parser error : attributes construct error ^ c01-sets.xml:640: parser error : Couldn't find end of Start Tag Token line 640

Re: Del Editor Confusion

2025-01-31 Thread M.Hall
; > 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 misunderstandings with the del editor. (this is long, sorry)

Quad-PW on macOS

2024-12-20 Thread M.Hall
I noticed that quad-pw wasn't changing with window resizes on macOS (Sonoma 14.7.2). Here's a patch; there's probably a better way to do it. I don't think it will break Linux builds, and it might help other OS (the BSDs maybe?), since not everyone has the same magic number for TIOCGWINSZ.. $ diff

Re: Quad-PW on macOS

2024-12-22 Thread M.Hall
Paul Rockwell writes: > There may be a side effect, though. With the option set and Mike's code inserted, ⎕PW will be set to whatever the current terminal width is, not the IBM APL2 default of 80. Yes. There are three settings that interact: - command line "--PW xx" - preferences "INITIAL-⎕PW

SVN 1816 Quad_RVAL::subfun_to_axis missing on macOS build

2025-01-11 Thread M.Hall
I saw a new SVN tag: trunk/ 1816 2 days j_sauermann enable subfunction syntax for ⎕RVAL $ svn info Path: . Working Copy Root Path: /xyz/APL/gnu-apl/SVN URL: http://svn.savannah.gnu.org/svn/apl/trunk Relative URL: ^/trunk Repository Root: http://svn.savannah.gnu.org/svn/apl Repository UUID:

Del Editor Confusion

2025-01-26 Thread M.Hall
I have some misunderstandings with the del editor. (this is long, sorry) $ apl ⍝ define a function ∇asd [1] 10 [2] 20 [3] ∇ ⍝ try it asd 10 20 ⍝ change the first line ∇asd[1]123∇ [2] ∇ ⍝ huh? wanted to change line 1, but got line 2. ⍝ it also didn't exit the editor ⍝ so run

Re: Quad-PW on macOS

2024-12-23 Thread M.Hall
or does not work on Mike's platform (which ?). Could someone > please test that? > > Thanks, > Jürgen > > > On 12/22/24 20:03, M.Hall wrote: > > Paul Rockwell writes: > > > There may be a side effect, though. With the option set and Mike's code > inserted,

Re: Quad-PW on macOS

2024-12-25 Thread M.Hall
INITIAL-⎕PW is a simple work-around to fix this. > > Best Regards, > Jürgen > > > On 12/23/24 22:47, M.Hall wrote not e: > > Yes, I see now the behavior is not quite right, is it? With INITIAL-⎕PW > disabled, the ⎕PW still starts up at 80, ignoring the window width even >

Re: Quad-PW on macOS

2024-12-23 Thread M.Hall
I > would think there would be some additonal work to make it work as Mike > wants. Personally having WINCH-SETS-⎕PW > (which sets ⎕PW to the window size) is the ultimate override - you get > what you're console column width is set for. Want 80? Set the console to 80. > >