Sujet : Re: Build Forth interpreter into a C/C++ application
De : no.email (at) *nospam* nospam.invalid (Paul Rubin)
Groupes : comp.lang.forthDate : 11. Feb 2025, 23:37:24
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <87seokumzf.fsf@nightsong.com>
References : 1
User-Agent : Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Buzz McCool <
buzz_mccool@yahoo.com> writes:
I happened to be reading an interview of Tom Zimmer
https://jimlawless.net/blog/posts/zimmer/ in which he states:
>
"When I work with other C programmers on large projects, I always
build in a Forth interpreter into the application, for debugging
purposes....
Would anyone have a "Hello, World!" type example of this technique?
I do see https://gforth.org/manual/Integrating-Gforth.html which ends
with an ominous "More documentation needs to be put here." :-)
I think these days the approach is less useful because of the
availability of external debuggers. C programmers these days are
comfortable with GDB, which gives source level debugging and
breakpoints. I'd be interested to know if any integrated Forth
debuggers supported that.
Gforth is quite heavyweight by Forth standards and if you wanted to use
Forth that way, you might be happier with something like pForth. Is the
idea to stop the application while poking around with Forth, or would
Forth be a task under an RTOS, or what?