fuzzballcat
Re:milliForth
on Tuesday November 07, 2023 @05:57PM (#38184259)
> The included py_autotype.py takes forever, but nothing outputs in the qemu vm as it is running.
Keep in mind, nothing SHOULD output while it's running, until you get to the very end and there's a 'hello world' printed.
This being said, the autotype's lethargy severely irks me. But I couldn't make it go faster, as pyautogui kept tripping up. If someone finds a better way (i.e. a way that isn't my first random thought), it will be much appreciated.
Re:milliForth
on Monday November 06, 2023 @06:50PM (#38171027)
Funnily enough, milliFORTH is now smaller than the Binary Lambda Calculus 383 byte implementation.
Re:milliForth
on Monday November 06, 2023 @06:41PM (#38170917)
Good thinking! I wouldn't have thought of that `xchg` one in DOCOL, very clever.
I'll futz around with making DOCOL's address as a word and see if I can make that work.
Re:milliForth
on Monday November 06, 2023 @06:36PM (#38170859)
Indeed! It's going to somehow be smaller than the 99 byte BF one...
Re:milliForth
on Monday November 06, 2023 @12:57PM (#38166073)
[Author here.] Indeed, sectorFORTH (as I have mentioned) was the primary inspiration and guide for this project! Ironically, in some places I even had a rather different design which converged on a more sectorFORTH-like design - it's really well put together.
I've removed some primitives further from milliFORTH, but I haven't touched the arithmetic base. I hadn't seen those issues on sectorFORTH though, very interesting - I will look into it!
Re:milliForth
on Monday November 06, 2023 @12:54PM (#38166030)
Author here! I was trying to be very careful about making sure to phrase things in a way that was clear I was referring to "real" languages (ones that are used for actual production purposes), but inevitably I forgot to do so where you've highlighted. I've updated the wording so it's more clear.