On Sat, Sep 27, 2025, at 6:04 AM, Anton Ertl wrote: > On Sat, Sep 27, 2025 at 01:03:29AM +0100, Ethan Azariah wrote: >> On Sat, Sep 27, 2025, at 12:57 AM, Ethan Azariah wrote: >> > vocabulary qxv only forth also qxv definitions >> > error: Undefined word >> > vocabulary qxv only forth also >>>qxv<<< definitions >> > >> > i just defined qxv, it shouldn't be undefined. > > I cannot reproduce this, neither with gforth-0.7.3, nor with the > current development version. E.g.: > > [b8:~:5041] gforth > Gforth 0.7.3, Copyright (C) 1995-2008 Free Software Foundation, Inc. > Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license' > Type `bye' to exit > vocabulary qxv only forth also qxv definitions ok > > [b8:~:5042] gforth -e 'vocabulary qxv only forth also qxv definitions' > Gforth 0.7.3, Copyright (C) 1995-2008 Free Software Foundation, Inc. > Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license' > Type `bye' to exit > order qxv Forth Root qxv ok
I can't reproduce it on my 64-bit tablet either, and I regularly use lines like this in 0.7.0. Of my various devices, the problem only occurs on a 32-bit x86 tablet, Android 7.1.2 (LineageOS 14.1), Gforth 0.7.9_20250305. I'm very surprised to have got a 32-bit tablet, but now I have and the older, rooted Android is good for tinkering. I remember from years ago some weird heisenbug affected only a 32-bit Android device. Do we want to track it down or do you just want to call 32-bit obsolete? I don't mind; Gforth is convenient but a bit too complex for me to really get into. I could run debugging binaries images or whatever if you want to supply them, but I don't want to use the Android SDK and I'm not yet used to using a debugger.
