Re: Problem compiling gforth from git on Fedora 39 with Wayland

files? You need wayland-protocols. > (BTW, there is an stb-devel package on fedora that ensures all the stb > headers are installed. And the gforth build also needs the texi2html > package installed.) Yes, thanks. That should all go into the install-deps.sh -- Bernd Paysan "If

Re: Using xt's

t1 t 0 cells + ! ' t2 t 1 cells + ! t 1 cells + @ execute It is often more convenient to define t1 and t2 beforehand, and then create t ' t1 , ' t2 , ' t3 , ' t4 , ' t5 , -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qq

Re: GForth for Windows

. My suggestion therefore is: try it, get used to it, and when you feel comfortably, switch. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Android C FFI / libtool

or do I need to set it up somehow? Yes, it is expected to work, and on Android, it doesn't — only cross compilation works. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Makefile.wayland syntax error

not found error. I'm now using the vpath directive to let make find the file itself (only for the %.xml files), and checking a bit more in configure+issuing a warning if the wayland protocol files are not found. -- Bernd Paysan "If you want it done right, you have to do it yourself" n

Re: Gforth not working in android 12 onward because of google changes

hat possible somehow? Probably, with an intent-filter. I'll check what's needed to handle this. I think the actions should be VIEW, EDIT (when the editor is added) and RUN. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn17

Re: Gforth not working in android 12 onward because of google changes

There is some way within the app to open up access to its internal files, and I'll try to use that to open up Gforth's directories. It is just too silly. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: C library

to C, and use the s type, so you can call s" my id" 1 callback-object mosquittoNew and the s type constructs a zero terminated C string out of that Forth string. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+

Re: Installationsproblem Gforth

n ich tun? Ich würde mal probieren, in install-deps.sh die zwei Funktionen zu definieren: install_linuxmint() { install_debian } install_gforth_linuxmint() { install_gforth_debian } Das sollte funktionieren, Linux Mint ist ja eine Debian/Ubuntu-Variante. Wenn's klappt, baue ich das ei

[bug #64436] Building from git on macOS Montery fails because install-deps.sh exports CC=gcc-11

Update of bug #64436 (project gforth): Status:None => Fixed Assigned to:None => paysan ___ Follow-up Comment #1: I added this code

[bug #64444] Building from git should NOT install swig in /usr/local!

Update of bug #6 (project gforth): Status:None => In Progress Assigned to:None => paysan ___ Follow-up Comment #1: I added code in git

Re: Precisions on the forth SWIG architecture: return by value structs

Am Dienstag, 13. Juni 2023, 01:32:08 CEST schrieb Bernd Paysan: > Am Dienstag, 13. Juni 2023, 00:17:14 CEST schrieb Bernd Paysan: > > Structs as arguments are already dealt with by a{*(type*)} (the argument- > > generating code would be then identical for a, but with struct as name)

Re: Precisions on the forth SWIG architecture: return by value structs

Am Dienstag, 13. Juni 2023, 00:17:14 CEST schrieb Bernd Paysan: > Structs as arguments are already dealt with by a{*(type*)} (the argument- > generating code would be then identical for a, but with struct as name). The Swig module from Gerald does handle this part already fine, i.e. it co

Re: f-rot not working? prio-B issue since frot works

t development snapshot, as explained below. We will not implement features in 0.7.3. >= how to know (for example f-rot) is NOT in GFORTH with a command which will >list all GFORTH WORDS? (= the output will show the f-rot is missing in the >listing) > > >Am Dienstag, 23. Ma

Re: f-rot not working? prio-B issue since frot works

romDebian 11. The manual refers to the current development snapshot. The download section here explains in brief words how to add the Debian repository fur the current snapshot. If you have feature requests, please do not request features that are already in. https://gforth.org/ -- Bernd Paysan

[bug #63201] compilation: [ 1 ]L cells + => #8 +

Update of bug #63201 (project gforth): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #63084] regexp-test.fs fails

Update of bug #63084 (project gforth): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #63801] add FCLEARSTACK analagous to CLEARSTACK

Update of bug #63801 (project gforth): Status:None => Fixed Assigned to:None => paysan Open/Closed:Open => Closed

[bug #64068] configure: C99 compatibility fix for -export-dynamic, assembler skip checks

Follow-up Comment #3, bug #64068 (project gforth): [comment #2 comment #2:] > I believe this is rejected by Apple Xcode (for a few versions now), and Clang 16. I'm submitting this now because we want to make similar changes in GCC (version 14, I hope). Clang still has the problems GCC had

Re: Embedding wishlist

hink you do not even need a change to Gforth > source code. You just need to do your own main (which you will do > anyway), link with engine/libgforth.la (or engine/libgforth-fast.la > etc.), perform your initialization and eventually call > gforth-engine(). Indeed. Add an argument for how large

[bug #63525] >time : unexpected behavior

Update of bug #63525 (project gforth): Assigned to:None => paysan Open/Closed:Open => Closed ___ Reply to this item at:

[bug #63730] The "see" command hangs forever on a default Ubuntu installation

Update of bug #63730 (project gforth): Status:None => Works For Me Assigned to:None => paysan ___ Follow-up Comment #1: This is (mostly)

Re: Split a string and characters

org/proposals/minimalistic-core-api-for-recognizers#reply-892 -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Split a string and characters

pe `bye' to exit s" foo bla" bl $split ok type bla ok type foo ok The Gforth manual on gforth.org is the upcoming Gforth 1.0 manual, so it contains features that weren't available in Gforth 0.7.3, or only available as loadable files. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

[bug #63084] regexp-test.fs fails

Update of bug #63084 (project gforth): Status:None => Fixed Assigned to:None => paysan ___ Follow-up Comment #1: Thanks for

[bug #62878] fork()'ed and then exit()'ing child procs are manipulating history file

Update of bug #62878 (project gforth): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #62878] fork()'ed and then exit()'ing child procs are manipulating history file

Update of bug #62878 (project gforth): Status:None => Fixed Assigned to:None => paysan ___ Follow-up Comment #1: Needs to add a

Re: [bug #62030] 'Malformed xchar' error, if fork'ed child throws

Am Montag, 8. August 2022, 09:31:55 CEST schrieb Stephan Rudlof: > How to avoid exit'ing child procs manipulating history file? You need to do a history flush-file before forking. Or better just flush the history directly in history.fs, when you write something. -- Bernd Paysan "If

Re: Gforth BLOCK 0

had block 0, which you just couldn't load from, so we changed the block numbering scheme to accommodate that. But the code was written around the assumption that block 0 does not exist. Fixed in current git head. -- Bernd Paysan "If you want it done right, you have to do it yourself" ne

Re: version 0.7.9_20220721 does not compile

> got gforth to compile. > > Any ideas what could be wrong? Since mkdir-parents fails, check if your build process has permissions to create these directories, and no stale leftovers from the last sudo make install are in the way. -- Bernd Paysan "If you want it done right, yo

Re: dumb TERM should not show status

Am Mittwoch, 27. Juli 2022, 22:25:46 CEST schrieb Tomas Hlavaty: > Is it possible to turn command line editing off manually now? > > Is it possible to turn echoing off manually now? Not easily. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id

Re: turn off history

your sever script using #! , you can't turn off this environment variable, because only one extra argument is allowed, so #! /usr/bin/env GFORTH_ENV=off is not valid. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+

Re: dumb TERM should not show status

There are some possibilities to make Gforth work better with the dumb terminal, e.g. by turning off command line editing end echoing (the dumb terminal is not capable of being turned into character mode), but this is not that high on the priority list. -- Bernd Paysan "If you want it done

Re: turn off history

Am Mittwoch, 27. Juli 2022, 13:13:08 CEST schrieb Anton Ertl: > On Wed, Jul 27, 2022 at 01:00:37PM +0200, Bernd Paysan wrote: > > Another question is: Should we open the history file later in the boot > > process, e.g. on entering interactive mode? There's no need to do that > &

Re: turn off history

that earlier. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Trouble using Gforth, having installed via homebrew on OSX

stent across terminal instances. You can put that into your ~/.bashrc, then it is persistent across instances. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Why hasn't gforth made it to 1.0 ... yet?

rising.com/2021/01/apt-key-is-deprecated-how-to-add.html I've updated my description here, Gerald, can you copy that into gforth.org? https://fossil.net2o.de/net2o/doc/trunk/wiki/get-it.md -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJz

Re: Building from scratch on Raspberry Pi 64-bit - install-info error

ng missing in the Pi operating system? I've run this successfully > before on NVIDIA Jetsons, which have arm64 / aarch64 CPUs like the > Raspberry Pi but run Ubuntu 18.04 LTS. That was just a glitch in the git repository (checkin of a updated documentation where the menu entries for the new

Re: Why hasn't gforth made it to 1.0 ... yet?

t2o.de/debian testing main The 0.x didn't mean “it's not ready“. We just started counting with 0, not with 1. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: Thi

[bug #62214] Building from source on Debian auto-installs outdated version

Follow-up Comment #5, bug #62214 (project gforth): Did you read INSTALL.md, section “build from tarball”? It's right there. ___ Reply to this item at:

[bug #62214] Building from source on Debian auto-installs outdated version

Follow-up Comment #3, bug #62214 (project gforth): install-deps.sh does not install the outdated Gforth (nor the fork of Swig), if you set BUILD_FROM to "tarball" before sourcing install-deps.sh. ___ Reply to this item at:

[bug #62030] 'Malformed xchar' error, if fork'ed child throws

Follow-up Comment #7, bug #62030 (project gforth): bye and (bye) are for leaving Gforth gracefully (the difference is that (bye) is a primitive). This means restoring the terminal. The thing we don't want. So we want to leave the forked process right at that point, not graceful, not restoring

[bug #62030] 'Malformed xchar' error, if fork'ed child throws

Update of bug #62030 (project gforth): Status: Confirmed => Fixed ___ Follow-up Comment #4: I added a bit code for handling a closed stdin more gracefully. The recommended way to handle

[bug #62030] 'Malformed xchar' error, if fork'ed child throws

Follow-up Comment #3, bug #62030 (project gforth): The way to do this in the current Gforth development version is by: require unix/libc.fs : test fork() if ( ... ) else [: ( ... ) ;] catch ?dup-if DoError 1 else 0 then exit() then ; fork() and exit() as C functions have

Re: GForth-EC isn't functional

gforth-0.7.3 to build Gforth-EC, as no development has been done for Gforth-EC, and we tried to separate the Gforth-EC kernel, but haven't tested if we did succeed other than “it compiles”. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X

[bug #61212] feature request: split out time to read and convert the time

Update of bug #61212 (project gforth): Status: In Progress => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #3: I changed the

[bug #59674] Stack on Status Bar Does Not Change Radix

Update of bug #59674 (project gforth): Status: In Progress => Wont Fix Open/Closed:Open => Closed ___ Follow-up Comment #5: We added code that

Re: gforth-0.7.9_20211125 tasker.fs broken

CE3BAC0 '-error > kernel/int.fs:608:5: 2 $7FF15CE3BB00 (') > tasker.fs:48:12: 3 $7FF15CEBA850 ' > > It works in gforth 0.7.3. Ok, seems to be a victim of the section code. Fixed in git head. Preferred multitasker is unix/pthread.fs in the

[bug #61212] feature request: split out time to read and convert the time

Update of bug #61212 (project gforth): Status:None => In Progress Assigned to:None => paysan ___ Follow-up Comment #1: [comment #0

Re: Crash with local variables and EXIT

Am Sonntag, 1. August 2021, 22:44:26 CEST schrieb Bernd Paysan: > Am Sonntag, 1. August 2021, 19:10:54 CEST schrieb Anton Ertl: > > > If you turn off WARNINGS, the problem > > > disappears, so it must be a warning problem. > > > > Very strange. > > My c

Re: Crash with local variables and EXIT

Am Sonntag, 1. August 2021, 19:10:54 CEST schrieb Anton Ertl: > > If you turn off WARNINGS, the problem > > disappears, so it must be a warning problem. > > Very strange. My current working theory is that reset-dpp is called somewhere within the warning mechanism. -- Bernd P

Re: Crash with local variables and EXIT

g problem. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Crash with local variables and EXIT

est ( flag -- ) > > 0 { var } > ?EXIT > 1 { var } ; > > false test > --8<-- > > This only happens when re-using a local variable name and only when > having the ?EXIT in between. Very strange that only reusing the local variable name triggers this. -- B

Re: Gforth pthreads support

really appreciate being able to > fully handle synchronization using message-passing only. > > cheers, > > David > > PS: looking at silk.fs, I may have been reinventing the wheel here. > > [1] https://gforth.org/manual/Pthreads.html -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Undocumented primitives

first 6 (mainly for porting > old code found on CLF or in papers). For rol/ror, I understand why that is a good idea, but drol is double cell, and the shifts should make no difference. I.e. if you have code like sw@ xx arshift .. w! this is just doing the right thing, regardless of cell s

[bug #60642] [Feature request] Make possible long tap options

Update of bug #60642 (project gforth): Assigned to:None => paysan ___ Reply to this item at: ___

[bug #60642] [Feature request] Make possible long tap options

Update of bug #60642 (project gforth): Status:None => Confirmed ___ Follow-up Comment #1: [comment #0 original submission:] > On Android, it's impossible to use the standard long tap

Re: I found bug?

Am Dienstag, 4. Mai 2021, 19:35:08 CEST schrieb Caroptions Caroptions: > Dear Gforth Community, > > I think I found bug: Yes, correct. I found this bug 5 days ago, see patch 58a3c88c to see-ext.fs -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o

Re: `s, ` undefined between versions 0.7.9_20201231 and 0.7.9_20210422?

the best way to define it is : s, ( addr u -- ) string, align ; -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: returning c string pointer to gforth

turn usable addresses: c-library test \c const char * foo="Hello World!"; \c const char * foo_x() { return foo; } c-function foo_x foo_x -- a end-c-library Try it: foo_x cstring>sstring type Hello World! ok -- Bernd Paysan "If you want it done right, you have to do it yourself&quo

Re: Cross compiling

Am Sonntag, 28. Februar 2021, 19:02:17 CET schrieb Francesco Ariis: > Il 28 febbraio 2021 alle 18:51 Bernd Paysan ha scritto: > > Am Sonntag, 28. Februar 2021, 17:04:16 CET schrieb Francesco Ariis: > > > Hello forthers, > > > > > > I was reading the

Re: Cross compiling

r older hardware as the Z80 or the Sharp LH79520? > Or would I be better off bootstrapping forth myself in assembly? For such older hardware, you need to port an assembler and the primitives (which is exactly what Klaus Kohl-Schöpe did for the 8086). -- Bernd Paysan "If you want

Re: cset seems to override the next byte

d r> c! ; : orc! ( x c-addr -- ) >r r@ c@ or r> c! ; -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

[bug #59674] Stack on Status Bar Does Not Change Radix

Follow-up Comment #3, bug #59674 (project gforth): We don't know what kind of number something we didn't identify actually is (ASCII code? Bitmask? Count of something?). Therefore, smart. falls back to . if it doesn't know. . is printed in the current base. The user probably knows. I think

[bug #57340] ekey goes into strange mode when reading shift-backspace

Update of bug #57340 (project gforth): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #59674] Stack on Status Bar Does Not Change Radix

Update of bug #59674 (project gforth): Status:None => In Progress Assigned to:None => paysan ___ Follow-up Comment #1: At the moment, this

Re: Minos2 terminal bug: rapidly repeated clear-and-redraw causes missed drawing

Am Donnerstag, 1. Oktober 2020, 15:39:55 CEST schrieb Ethan Gardener: > On Thu, Oct 1, 2020, at 1:54 PM, Bernd Paysan wrote: > > 0 is the "change nothing" pseudo-color, 6 is the default pseudo-color and > > 7-15 are actual colors of choice. > > Thanks! I've chang

Re: Minos2 terminal bug: rapidly repeated clear-and-redraw causes missed drawing

ther 0color after the cr. 0 is the "change nothing" pseudo-color, 6 is the default pseudo-color and 7-15 are actual colors of choice. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: Minos2 terminal bug: rapidly repeated clear-and-redraw causes missed drawing

ted place. > > Aha! Everything after the highlight is blank. If the current block is block > 5, there's 5 entries, if block 4, 4 entries, if 30, 30, etc. The highlight is probably done wrong. It should use ATTR!, not direct escape sequences. -- Bernd Paysan "If you want it don

Re: Is it possible to hook into the prompt?

defers prompt ; ' my-prompt is prompt -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: amd64 missing addressing modes

pdf Page 21. Callee-saved registers can not be used freely. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature.asc Description: This is a digitally signed message part.

Re: amd64 missing addressing modes

X move. It is only a problem if you move to AX. I added some code to fix it, the solution is to add an offset 0 if it is this move. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ signature

Re: amd64 missing addressing modes

This here works: abi-code test ok 1 ax cx *4 i) dx mov ok 1 3 ax cx *8 di) dx mov ok 1 ret ok 1 end-code see test ABI-Code test 7F38B25582B0: mov rdx,[rax][rcx*4] 7F38B25582B4: mov rdx,$03[rax][rcx*8] 7F38B25582B9: ret end-code Your example doesn't work, though. Looks lik

[bug #48406] forth-block-mode marks buffer as modified when I visit a file

Update of bug #48406 (project gforth): Status: Confirmed => Fixed Assigned to:dvdkhlng => paysan Open/Closed:Open => Closed

Re: Gforth git-master swig dependency

Am Sonntag, 16. August 2020, 12:39:23 CEST schrieb David Kuehling: > >>>>> "Bernd" == Bernd Paysan writes: > > Am Sonntag, 16. August 2020, 11:07:18 CEST schrieb David Kuehling: > >> So here I'm somewhat stuck. Google doesn't turn up any usable > &

Re: Gforth git-master swig dependency

Am Sonntag, 16. August 2020, 11:07:18 CEST schrieb David Kuehling: > So here I'm somewhat stuck. Google doesn't turn up any usable > information about how to get a forth-enabled Swig. ./install-swig.sh ./install-freetype-gl.sh Look at install-deps.sh, if you have a Debian system. --

[bug #58922] gforth 0.7.3 fails to build on Ubuntu 20.04 unless gdb is installed

Update of bug #58922 (project gforth): Status:None => Wont Fix Assigned to:None => paysan Open/Closed:Open => Closed

Re: GForth in F-Droid repository?

what the app store managers are like or who [re]publishes > apps on them, so they make me nervous. I'd prefer to download the apk > directly from gforth.org. At the moment, I put the apks here, but I can also push them to the Gforth Snapshots, like the tarball and the Windows setup.exe. https://ne

Re: [PATCH] arm: beagle: fix possible null dereferences

Am Sonntag, 2. August 2020, 23:28:04 CEST schrieb Geyslan G. Bem: > Make assertions before pointer dereference. Looks ok to me. I don't know if the beagle-board port of Gforth still compiles, though. Back then, I copied some code from Ti, to get it to work quickly. -- Bernd Paysan "If

Re: GForth in F-Droid repository?

M-SCRATCH in gforth/arch/arm/android. This assumes you have a working Android SDK build environment with gradle, including signing key. The BUILD- FROM-SCRATCH also shows how you integrate your own app similar to net2o. -- Bernd Paysan "If you want it done right, you have to do it yourself"

Re: Bug report

Am 4. Juli 2020 18:21:47 MESZ schrieb Ian Bell : >Using Gforth 0.7.9_20200611 > >Type a single letter t or T followed by return > >Gforth freezes No, it waits for a TCP connection on port 4444. -- Bernd Paysan "If you want it done right, you have to do it yourself" ne

Re: lshift bug

t auf allen Byte-Maschinen die Anzahl der Bits. In den Environmental Queries gibt es ADDRESS-UNIT-BITS, das + CELLS gibt die Anzahl Bits pro Zelle. Zuverlässig. Überall. Leider doof zu benutzen, weil die Environmental-Queries halt doof sind. Aber so für eine Konstante akzeptabel. -- Bernd Paysan "If

Re: -infinity and REPRESENT

roduced "-inf" and f1=0 (positive), > > f2=0 (not valid); other libc implementations might lead to different > > results. > > Sorry, what are f1 and f2? flag1 is sign (-1 when negative), flag2 is valid (0 when invalid). -- Bernd Paysan "If you want it done r

Re: Question about libcc.fs and finding path of dynamic library

it does > not! > > I know this is a complex problem and i am asking a lot here but any help > would be appreciated! inetd probably has some jailing to prevent you to access ~/.cache or so. Anyways GFORTHCCPATH is the environment variable that is used as search path for librari

Re: s>number? beginner question

S" with space and then the string. s" 123" s>number? .s <3> 123 0 -1 ok 3 The non-standard extension with the string recognizer you are using doesn't need the space, and includes it in the string when you have it there. "123" s>number? .s <3> 123 0 -1

Re: Unexpected emit Behaviour

uld expect. > > > The Android behaviour not what I was expecting and wonder if it is a bug. > > > Typing: > > 128 emit > > > ... should show the issue. Thanks for reporting this bug. Fixed in git, will get out with the usual release cycle. -- Bernd Paysa

Re: How to get stdin that is passed to Gforth from command line in Debian for example?

id to read all from that file. Example: echo "This is a test" | gforth -e "stdin slurp-fid type bye" So your (get-ext-stdin$) is : (get-ext-stdin$) stdin slurp-fid ; -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy

[bug #57741] Strange begin drop again ;

Follow-up Comment #4, bug #57741 (project gforth): [comment #3 comment #3:] > Ok, I'll fix it. 2DROP, FDROP and RDROP are also relevant, anything else? 2RDROP. All LP+ variants. ___ Reply to this item at:

[bug #57741] Strange begin drop again ;

Follow-up Comment #2, bug #57741 (project gforth): [comment #1 comment #1:] > We could fix this by adding a memory access in DROP (and some other words), but I am not sure if this is worth the effort and the slowdown. With the debugging engine (gforth), it's probably worth it. We don't do TOS

[bug #57340] ekey goes into strange mode when reading shift-backspace

Update of bug #57340 (project gforth): Status: Confirmed => Fixed ___ Follow-up Comment #8: I added a fix for both problems (not recognizing shift-tab, sticking in line-mode style when the

[bug #57340] ekey goes into strange mode when reading shift-backspace

Follow-up Comment #5, bug #57340 (project gforth): [comment #3 comment #3:] > On another machine (Ubuntu submodule of Windows 10) it is: > lrwxrwxrwx 1 root root 15 Jun 1 2019 /etc/alternatives/x-terminal-emulator -> /usr/bin/lxterm But you likely aren't using that in the WSL, because there's

[bug #57340] ekey goes into strange mode when reading shift-backspace

Update of bug #57340 (project gforth): Status:None => Need Info Assigned to:None => paysan ___ Follow-up Comment #1: Can't reproduce at

[bug #57324] does not install on Windows 10 LSM

Follow-up Comment #4, bug #57324 (project gforth): Can you do rm -rf lib make libcc and provide me with the output log if that fails? ___ Reply to this item at:

Re: Android Gforth not displaying non-ASCII characters

Am Sonntag, 1. Dezember 2019, 19:23:52 CET schrieb Marcos Cruz: > Could Gforth be compiled in Termux or other terminal application? I > guess not. That could be possible, after all, the terminal applications just run normal Linux binaries. -- Bernd Paysan "If you want it done righ

[bug #57324] does not install on Windows 10 LSM

Update of bug #57324 (project gforth): Status:None => Works For Me Assigned to:None => paysan ___ Follow-up Comment #1: Dependencies to

Re: Android Gforth not displaying non-ASCII characters

on > mark or omitted. I tried it also on a recent version of Android, same > problem. > > Is it a Gforth's issue, or maybe additional system fonts are needed? Gforth gl-terminal is for ASCII and a few special characters only. That's intentional, it should be simple. -- Bernd Paysan "

Re: [bug #57324] does not install on Windows 10 LSM

alid libtool archive > > The same error also flags libgfsocket.la libgfmmap.la libgfserial.la > libgffilestat.la libgftime.la libgflibffi.la > > > How can the libtool errors be resolved? The install script that works (and is used for continuous integration on a Debian image) is install-d

Re: Gforth not working on Android 5.0.1

version runs fine on my 64 bit devices. I compile the C code with API set to 19, i.e. KitKat, which also shouldn't be a problem if you have anything newer. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t

Re: Gforth not working on Android 5.0.1

Am Dienstag, 19. November 2019, 12:46:55 CET schrieb Marcos Cruz: > En/Je/On/In 2019-11-19 11:52, Bernd Paysan escribió/skribis/wrote/scrit: > > Debian has an android-tools-adb package, that would only install adb, > > nothing else. > > I already did that on my Debian. Bu

Re: Gforth not working on Android 5.0.1

e. >From my side, I can try installing an old Android in VirtualBox or running Gforth in the Android emulators that come with the SDK. One more option is to install a log viewer right on the phone, like Logcat Reader. -- Bernd Paysan "If you want it done right, you have to do it yourself&qu

  1   2   3   >