21:06:33
##forth
<
lisbeths>
please make sure that crc gets to view this so he can tell me what he thinks of it. it is based on dc by ken thompson see here: https://man.freebsd.org/cgi/man.cgi?query=dc dc was originally made as a memory safe rpn virtual machine for the pdp7 by ken thommpson and he named it desktop calculator to hide from his bosses that he was making operating systems for the pdp7
21:28:17
##forth
<KipIngram>
lisbeths: crc will definitely see what you posted there. Don't worry - we're generally a pretty laid back bunch around here. Just being interested in Forth is pretty much enough to make us happy. :-)
21:29:47
##forth
<tpnix>
lisbeths, Forth is so unpopular thesedays that anyone who hassles you is just a troll. All Forths are good as they show continuing Forth interest
21:31:53
##forth
<tpnix>
lisbeths, I think most of the Forths these days are written in C, and some arent bad, take 'muforth' for instance. It's a tethered Forth and kind of unique, the author has been working on it for 20 years
21:33:07
##forth
<tpnix>
lisbeths, I use Mecrisp-Stellaris Forth which is written in 100% assembly and is a dedicated embedded Forth, rare and refined, and now abandonded by the author :(
21:52:07
##forth
<crc>
lisbeths: I'm not a big fan of register based systems, but this looks reasonable (though 256 registers for data & 256 for pointers seems a bit high given the very limited RAM)
21:53:32
##forth
<crc>
do you have any example programs for it?
21:58:39
##forth
<lmt>
pretty sure that dc was written because it being the 70s, calculators were not generally available
21:58:43
##forth
<lmt>
and also not by ken thompson
22:09:34
##forth
<skvery>
lisbeths Are you sure Matthias abandoned Mecrisp?
22:10:09
##forth
<skvery>
Are any of you part of Meshcore?
22:12:10
##forth
<tpnix>
skvery, I made that claim re Matthias, he stopped any development a year ago as hes been putting his energy into FPGA. Hes still developing Mecrisp-Quintus on riscv
22:13:29
##forth
<tpnix>
skvery, he appointed a new maintainer for Mecrisp-Stellaris and bumped the 2.x series to 3.0 for the occasion
22:13:39
##forth
<skvery>
tpnix Well, it is stable and the sources are publicly available...
22:14:11
##forth
<tpnix>
skvery, yes, Mecrisp-Stellaris will live on forever as is, I use it every day and make tooling for it
22:15:11
##forth
<tpnix>
Mecrisp-Stellaris was released in 2014 and I've been using it since then
22:15:47
##forth
<skvery>
I suspect it is one of the fastest Forth implementations.
22:16:18
##forth
<tpnix>
skvery, youre right, and the compiler is awesome, Matthias is a assembly genius
22:18:31
##forth
<skvery>
Maybe building a FPGA that is optimised for Mecrisp is a good development. (Is that not what C Moore wanted to do?)
22:22:46
##forth
<tpnix>
skvery, maybe, but Im a electronics guy who does embedded, I'm not a programmer
22:23:10
##forth
<skvery>
I am very interested in Mecrisp-core for nrf5* series - to integrate it with Meshtastic.
22:25:07
##forth
<tpnix>
we have support for two models, nRF51822 and nrf52832
22:26:46
##forth
<skvery>
Mecrisp needs a marketing department. The "interpreter" is extremely fast and the Forth and Basic history is really holding Mecrisp back. It so powerful to be that close to the hardware!
22:29:30
##forth
<tpnix>
skvery, Ive just finished a tool that adds CMSIS-SVD tp Mecrisp-Stellaris, but doesnt change it in any way
22:30:19
##forth
<tpnix>
so all the peripheral registers are available as labels according to the CMSIS nomeclature
22:30:46
##forth
<tpnix>
it is of course only useful to embedded users
22:32:39
##forth
<skvery>
nrf52*
22:43:17
##forth
<crc>
lisbeths: charles.childe.rs/lisbeths-vm.tar.gz has an assembler (in python) and a hello, world example for your vm