On Sun, 02 Nov 2025 14:40:07 +0000
[email protected] wrote:
> Dear AmForthers,
>
> I liked Erich's "AmForth Weekend" format, so I'm sticking with
> it. This is AmForth Weekend 4. This weekend's motto is "Try not to
> break anything".
>
> The focus is on AVR8, amforth-shell.py and the website.
>
> No release yet, but some activity in trunk.
>
> Let me know what works, and what does not.
>
> Best wishes,
> Tristan
>
> # SUMMARY
>
> ## AMFORTH-SHELL.PY
>
> amforth-shell.py has had some syntax warning fixes and one new
> feature. The syntax was correct at the time, but python has moved on.
>
> A directive #stack has been added. This toggles on and off displaying
> the contents of the mcu data stack as a prompt (if the word .s exists
> on the device)
>
> ## AVR8
>
> Within the existing codebase, some minor fixes to a handful of .asm
> files that avra was rightly flagging with warnings about misalignment
> in word name .db statements. Whilst avra padded these out correctly,
> better to fix.
>
> *Request for help* - I'm not a MS windows user, but I am keen that the
> existing build system still works for MS windows. If you are a MS
> windows
> user I would be grateful if you could try and build AmForth from trunk
> and let me know if it still works for you.
>
> ## WEBSITE
>
> This wasn't top of my initial list of things to look at. However,
> without documentation, prebuilt hex files are of diminished
> use. AmForth's documentation is a very special resource. Time and
> reST/Sphinx (the system that turns documentation source into html and
> the website), however, have moved on. Running the documentation
> through a modern Sphinx broke a few things on the site. These have
> been fixed. Some missing svg files that were produced from dia format
> files were salvaged from the 6.8 release. There remain some broken
> links to missing pdfs/frt on the recognizer page. The documentation
> source is available, but rebuilding requires a chain of personal
> system upgrades I'm not quite ready for yet.
>
> As an apprentice piece in writing something with reST, I've added a
> post on the Opinion page.
>
> ## WHAT IS NEXT
>
> Reference card
> Prebuilt hex files for AVR8
>
> ## COMMITS
>
> r2458 change of maintainer
>
> r2459 minor fixes to amforth-shell.py syntax warnings fixed, modify #!
> to a less fragile one
>
> r2460 adds directive #stack to amforth-shell.py #stack toggles whether
> the mcu data stack is displayed to left of input prompt > Default is
> no.
>
> r2461 fix .db padding warnings (from avra)
>
> r2462 website update
>
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>
>
Thanks Tristan. Efforts much appreciated.
You didn't ask for them, but I have a couple of ideas for
amforth-shell.py:
1.
Have an "#ifndef FORTHWORD forthword.frt" directive. "#ifdef" also.
2.
Directives that take a path or filename will look for a partial path.
i.e: #require project1/main.frt
#require project2/main.frt
are considered different files.
If either of these can be achieved by some other means, then please
chip in. I am aware of "#cd".
--
Regards,
Martin Nicholas.
E-mail: [email protected] (Address will be valid throughout 2025).
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
[email protected]
https://lists.sourceforge.net/lists/listinfo/amforth-devel
