home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.forth      Forth programmers eat a lot of Bratwurst      117,927 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 117,072 of 117,927   
   Paul Rubin to Buzz McCool   
   Re: Build Forth interpreter into a C/C++   
   11 Feb 25 14:37:24   
   
   From: no.email@nospam.invalid   
      
   Buzz McCool  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?   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca