Hi
> Hi.
>
> how can I see what word a defered word will execute?
>
> gforth:
>
> defer test ok
> : xxx 11 22 33 . . . ; ok
> xxx 33 22 11 ok
> .s <0> ok
> ' xxx is test ok
> test 33 22 11 ok
> .s <0> ok
> see test
>
> : xxx
>11 22 33 . . . ;
> latestxt
> Defer test
> IS test
> ok
Hi Pito.
Looks like a kind of disassembler.
So ff is subroutine threaded forth?
amforth is token threaded code (TTC).
Here we want an disforther. ;-)
Thanks for the info. Michael
Am 18.09.2010 um 10:08 schrieb pito:
> Michael,
> so I fired up ff and this is what I can see:
>
> ok<$,ram>
> see
Michael,
so I fired up ff and this is what I can see:
ok<$,ram>
see see
26ea eca0 f00c call '
26ee eccf f00c call cr
26f2 df20 rcall (see)
26f4 50ed
26f6 10ee
26f8 e1fc bnz 26f2
26fa 50ed
26fc 50ed
26fe 0012 return
ok<$,ram>
see drop
0e4c 50ed
0e4e 50ed
0e50 0012 return
ok<
Micheal, thanks!
> So replace here with dp if you use amforth-4.1
> please.
and update words definition on the amforths web as well..
> This flashforth SEE is interesting, but I cannot
> run it, no pic here.
> What is its output?
YES the ff is interesting, indeed. Maybe sharing ideas between them
Am 18.09.2010 um 01:05 schrieb pito:
> Hi Michael,
> few Q (sorry, I am an forth language illiterate):
> a) how the "here" knows what to deliver - next free address of flash
> or next free address from ram?
Oh, I'm sorry. Its in amforth-3.6.
amforth-3.6
here == next free address of flash
heap ==
Hi Michael,
few Q (sorry, I am an forth language illiterate):
a) how the "here" knows what to deliver - next free address of flash
or next free address from ram?
b) I saw see in flashforth and I did run it - it is very short, can
that be ported to amforth (see ff36 folder) somehow?
c) would it be p
