Re: [Amforth] amforth-shell.py bugfix

[Enoch <ix...@ho...>]

Matthias Trute <mt...@we...> writes:

> Hi,
>
>> I added an #include-once directive and let it default to "no" (current
>> behavior).  Also added was a program argument to change the default
>> behavior if one so desires [me]. Testing done as well.
>> 
>> http://pastebin.com/5Mfrvzdw
>
> Applied. And Thanks to Keith for discussion. 
>
> btw: I agree with Keith that the shell is a tool to make live
> easier, but I won't make it a must-have tool. 

Let's make it an essential convenience then :-)

I have two more developments planned for the shell, one easy -- one
tough... The tough one I mentioned already, which is, use a library like
PyUSB to control the popular JTAG Mk II ICE the Forth way.

Let's mention the easy one, perhaps we shall have a volunteer coming
up. Let's say we need to send new Forth code to a client to introduce a
new feature or bug fix. The client, unfortunately, cannot be expected to
have a sophiticated uploader tool like our Python based shell. All
he/she has is something akin to minicom (Linux), tera-term (Windows),
etc.

A simple solution is to add a "distiller" mode to the shell where
alongside its normal work it would capture to a file all the characters
uploaded to the SUT (system under test), that is, past name substituion,
past all #include's, etc. The end result would be one compact file which
our client will be able to upload via his simple terminal program.

Anyone?

Regards, Enoch.