A 3-INSTRUCTION FORTH FOR EMBEDDED SYSTEMS WORK Illustrated on the Motorola MC68HC11 by Frank Sergeant
https://pages.cs.wisc.edu/~bolo/shipyard/3ins4th.html#:~:tex....
131–138 of 138 posts
A 3-INSTRUCTION FORTH FOR EMBEDDED SYSTEMS WORK Illustrated on the Motorola MC68HC11 by Frank Sergeant
https://pages.cs.wisc.edu/~bolo/shipyard/3ins4th.html#:~:tex....
Earlier quoted context omitted.
Haskell, Julia, Rust, Lisp, and Forth are 'esoteric' enough to create an in-crowd, who are quite often deluded by imagined miraculous solutions to people's problems. Please repeat after Fred Brooks: there ain't no silver bullet. To a certain extent this goes on outside programming languages per se: OOP, Gang of Four, Agile match the pattern as well.
Feel APL similar in-crowd member too, though perhaps even more niche
Earlier quoted context omitted.
I know it's a lot of fun writing Forths and that's how most people tend to experience Forth, but I like to urge people to actually build applications on Forth. Understanding Forth by writing applications is probably the best way to get a feel for Forth.
Is there any "battery-included" ANS Forth (more or less like Python/Go) which provides access to concurrency, networking, database, GUI, etc? Not an embedded device programmer, but mostly deals with frontend apps, and occasionally backend, so those are very relevant to me. Or perhaps use "non-traditional" Forths like 8th ( https://8th-dev.com ) or Factor ( https://factorcode.org )?
8th is a great not-Forth. Highly recommended because of how practical is.
Earlier quoted context omitted.
Feel APL similar in-crowd member too, though perhaps even more niche
Yup. Also HolyC (literally a religious undertaking), but the crowd had only one person, and he is no longer with us.
We used to have our Forth-like system back in 1994, with a virtualized NEXT point, so we had execute, interpret, compile and two link stages behaviors for each word. This allowed produce making an optimizing linker, which produced very tiny .COM-files. I still have source code for it.
I think this idea can quite easily be taken to the extreme, and allow adding things like - type checking - debugging - SSA IR generation (say, for LLVM optimizer) - lots run-time checks (for tests)
So I believe a Forth system can be made quite safe.
The author complains about not having local variables, but most decent Forth environments have them. It is not difficult to have local variables in Forth, just use a library or compiler that provides them.