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,073 of 117,927    |
|    Buzz McCool to Paul Rubin    |
|    Re: Build Forth interpreter into a C/C++    |
|    11 Feb 25 18:06:08    |
      From: buzz_mccool@yahoo.com              On 2/11/25 14:37, Paul Rubin wrote:       > ... Is the       > idea to stop the application while poking around with Forth, or would       > Forth be a task under an RTOS, or what?              I'm unclear on the whole concept Tom Zimmer was advocating so I was       asking if anyone had examples.              I have a bare metal type embedded system I'm working on where I can       command it from Ethernet. It has a serial console port. Maybe your first       idea would be an example where I could command it to stop and jump into       a Forth ok prompt so I could type commands into the serial port and see       debug output there.              Your second idea is along the lines of the Gforth/ATLAST concept where       Forth is a scripting language for a C/C++ application. I have another       Linux based embedded system that has some pieces that are always       changing. Maybe a Forth task inside a C/C++ program that would pick up       changeable scripts from the SD Card would be better than constantly       recompiling my C/C++ application and re-flashing main memory.              --- 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