Re: [Amforth] amforth-shell.py patch proposal

Hello Matthias & all: > Matthias Trute writes: >> That makes sense. But appl_own.py as the filenname. There should >> be better ones. Or a more generic approach. I'm not a python expert, >> but many python directories contain a file named __init__.py to do >> something useful. > > Seems too "

Re: [Amforth] amforth-shell.py patch proposal

Matthias Trute writes: > Enoch, > >> I said, how nice it would be if amforth-shell would do it for me just >> like it does with Atmel's register/bit defs. > > That makes sense. But appl_own.py as the filenname. There should > be better ones. Or a more generic approach. I'm not a python expert

Re: [Amforth] amforth-shell.py patch proposal

Enoch, > I said, how nice it would be if amforth-shell would do it for me just > like it does with Atmel's register/bit defs. That makes sense. But appl_own.py as the filenname. There should be better ones. Or a more generic approach. I'm not a python expert, but many python directories conta

Re: [Amforth] Wish to FORGET

Erich Waelde writes: > Hi Enoch, > > On 03/04/2013 04:03 AM, Enoch wrote: > >> The code at will expire in 4 weeks. > > See? In 4 weeks the code is gone. If you had added it to the message > in the first place, then anyone could find it even in years, if > the mail a

Re: [Amforth] amforth-shell.py patch proposal

Matthias Trute writes: > Hi Enoch, > >> >> As I promised to generalize crc8.frt (#1) a question was raised how would >> the user configure it to its use, namely, select the generating >> polynomial byte and the needed bit order (#2). >> >> I answered the question through the following amforth-sh

Re: [Amforth] Wish to FORGET

Hi Enoch, On 03/04/2013 04:03 AM, Enoch wrote: > The code at will expire in 4 weeks. See? In 4 weeks the code is gone. If you had added it to the message in the first place, then anyone could find it even in years, if the mail archive is still available on the net

Re: [Amforth] Variations on .S

Matthias Trute writes: > Hi, > >> Hello Erich & all, >> >> The focus of my .s comment was on Matthias non standard stack listing >> order, > > Since there is no standard format, my variant cannot be non-standard. > Thats impossible by definition. > > I updated http://amforth.sourceforge.net/TG/r

Re: [Amforth] Wish to FORGET

Matthias Trute writes: > Hi, > >> Indeed, your suggested use of MARKER is what I anticipated but I have to >> agree with you, it would be too difficult/dangerous for an average >> programmer to try. > > I wrote "difficult" not "too difficult" A subtle difference. > >> Hence, let us revisit FORGET

Re: [Amforth] amforth-shell.py patch proposal

Hi Enoch, > > As I promised to generalize crc8.frt (#1) a question was raised how would > the user configure it to its use, namely, select the generating > polynomial byte and the needed bit order (#2). > > I answered the question through the following amforth-shell.py > improvement which introdu

Re: [Amforth] Wish to FORGET

Hi, > Indeed, your suggested use of MARKER is what I anticipated but I have to > agree with you, it would be too difficult/dangerous for an average > programmer to try. I wrote "difficult" not "too difficult" A subtle difference. > Hence, let us revisit FORGET. > I agree with you again that with

Re: [Amforth] Variations on .S

Hi, > Hello Erich & all, > > The focus of my .s comment was on Matthias non standard stack listing > order, Since there is no standard format, my variant cannot be non-standard. Thats impossible by definition. I updated http://amforth.sourceforge.net/TG/recipes/Dumps.html with Erich's examples.

[Amforth] amforth-shell.py patch proposal

Hello Matthias & all: As I promised to generalize crc8.frt (#1) a question was raised how would the user configure it to its use, namely, select the generating polynomial byte and the needed bit order (#2). I answered the question through the following amforth-shell.py improvement which introduce