Re: [Amforth] ALSO

2014-01-27 Thread Matthias Trute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sam, > In avrforth http://krue.net/avrforth/control/ there's a separate > `;` and `;;`. Would it be possible to add a `;;` that behaves like > the `;` in avrforth? I have no idea how a tail call recursion elimination would look like in an ITC for

Re: [Amforth] ALSO

2014-01-27 Thread Sam Putman
On Sun, Jan 26, 2014 at 11:39 AM, Matthias Trute wrote: > > > Of course you'll blow the return stack pretty fast without tail > > call elimination. I confess I've looked at all the available Forths > > for the AVR so I can't remember if AmForth provides this > > capability. > > The amforth compil

Re: [Amforth] ALSO

2014-01-26 Thread Matthias Trute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sam and Enoch, >> >> Not for me. I have lots of mutually recusive word definitions >> like: >> >> : A ... ; \ calls B : B ... ; \ calls A >> >> and spending one Edefer per each Nobody talks about Edefers, just use Idefers (the technique to cr

Re: [Amforth] ALSO

2014-01-26 Thread Sam Putman
On Sun, Jan 26, 2014 at 8:39 AM, Enoch wrote: > Hi Matthias, > > Matthias Trute writes: > > > >> Their forward reference implementation is here: > >> openfirmware/forth/kernel/forward.fth > > > > I don't understand the code. > > > >> > >> Should we do likewise? > > > > DEFER is "good enough". >

Re: [Amforth] ALSO

2014-01-26 Thread Enoch
Hi Matthias, Matthias Trute writes: > >> Their forward reference implementation is here: >> openfirmware/forth/kernel/forward.fth > > I don't understand the code. > >> >> Should we do likewise? > > DEFER is "good enough". Not for me. I have lots of mutually recusive word definitions like: : A

Re: [Amforth] ALSO

2014-01-26 Thread Enoch
Hello Matthias, Matthias Trute writes: >> True indeed, that is how gForth and others do it but they have full >> support of vocabulary in the kernel while we don't. > > Huh? AmForth order: ~~ > order 16 2 16 86 ok gForth order: ~ order Forth Forth Root Forth o

Re: [Amforth] ALSO

2014-01-26 Thread Matthias Trute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Enoch, > True indeed, that is how gForth and others do it but they have full > support of vocabulary in the kernel while we don't. Huh? > Mentioning c.f.l I started following it recently having discovered > that EMACS GNUS can handle RSS feeds

Re: [Amforth] ALSO

2014-01-26 Thread Enoch
Hi Matthias, Matthias Trute writes: > Hi Enoch, > >> Shouldn't ALSO be corrected as follows: > > ANS94 has in section 16.6.2.0715 ALSO the following specification > > "Transform the search order consisting of widn, ... wid2, wid1 (where > wid1 is searched first) into widn, ... wid2, wid1, wid1.

Re: [Amforth] ALSO

2014-01-26 Thread Matthias Trute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Enoch, > Shouldn't ALSO be corrected as follows: ANS94 has in section 16.6.2.0715 ALSO the following specification "Transform the search order consisting of widn, ... wid2, wid1 (where wid1 is searched first) into widn, ... wid2, wid1, wid1. An a

[Amforth] ALSO

2014-01-26 Thread Enoch
Hello Mattias & All: Shouldn't ALSO be corrected as follows: diff --git a/core/words/also.asm b/core/words/also.asm index 08cf258..33a6c2d 100644 --- a/core/words/also.asm +++ b/core/words/also.asm @@ -1,6 +1,6 @@ -; ( -- ) +; ( "name" -- ) ; Search Order -; Duplicate first entry in the curren