wolfgangr
wolfgangr
@zeroflag Attila, thank you for response. Glad to see that I'm not walking alone :-) I work on a fork of tasmota and keep documenting a journal of my considerations...
punyforth is my current favorite, above all because of its existing multitasking implementation. I hope this will help me to weave it ito the task management of arduino & tasmota....
> If you want to have all these functionality (GPIO, netcon, etc) you would need to change these C functions to call the arduino equivalents of the RTOS code. Yes,...
> Is code in loop() supposed to return? Yes, of course. That's what cooperative multitasking is all about. > What happens if you put an infinite loop inside the loop?...
However, my considerations go beyond that: What about the inner interpreter? The goal at the end is to **implement drivers in forth** and **hook them into tasmota**. I think your...
So, the **hook** question from above generalizes to: How can I **suspend** from and **resume** to FORTH without screwing the C environment? I think the compiled C-code assumes some CPU-registers,...
Hi @holinepu great to have a response from you. Some findings from other forth'es: Cforth uses a elaborated host based forth compilation machine https://github.com/MitchBradley/cforth/blob/esp32-v1.0/src/cforth/embed/BuildProcess.txt Thus it has a bunch of...
> yes, I've done some work on punyForth 2 months ago. > I can compile the program in RAM and then move it to flash momery. > Gradually the program...
Agree about PIO. Nice Edit and browse tool, but heavy layer of obfuscation / opaqueness. Had maybe some 5 crashes till now, one X-server freeze (on a debian - hadn't...
What do you think of my forth idea? If we could implement any higher level driver stuff in a higl level language, that might ease out things a lot. So...