Hello Mattias,
>> Yes, I suggest a run-time optimization step "with no going back"
>> where all FFdefer word calls would be reprogrammed to reach
>> immediately the FFdefer destination (skip the FFdefer word call).
>
> I think it's not necessary to have a special (defer) runtime, the
> developer c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Enoch,
> Yes, I suggest a run-time optimization step "with no going back"
> where all FFdefer word calls would be reprogrammed to reach
> immediately the FFdefer destination (skip the FFdefer word call).
I think it's not necessary to have a specia
Hello Matthias,
Matthias Trute writes:
> Hi Enoch,
>
> My recent changes were a code compacting, since defers and values are so
> close to each other.
>
>> May I suggest a new defer object, say, "FFdefer" that would be implemented
>> like "Edefer" except that if a certain global boolean, say, Fa
Hi Enoch,
My recent changes were a code compacting, since defers and values are so
close to each other.
> May I suggest a new defer object, say, "FFdefer" that would be implemented
> like "Edefer" except that if a certain global boolean, say, FastForward, is
> set then the first "xt_FFdeferfetch"
Hello Matthias & All:
As you are now improving the defer mechanism how about offering a way in
some instances to eliminate it completely?
One of Edefer important uses is to resolve forward references as AmForth
has no linkage editor (aka, linker). For example:
file1.frt
=
Edefer truck
:
Am Sonntag, den 12.01.2014, 15:50 +0700 schrieb v...@eml.ru:
> Hi, Matthias,
> I think error can be fixed by dividing mcu_maxdp value by
> two.
> Something like this:
Yes, thats right. I was not clear in what is difficult to
fix, sorry. The information that is used to calculate the
free cells com
Hi, Matthias,
I think error can be fixed by dividing mcu_maxdp value by
two.
Something like this:
: .res ( -- )
base @ >r
decimal
ver ." running at " f_cpu &1000 um/mod . drop ." kHz
" cr
s" mcu-info" environment? if
2 + @i 2/ dp -
." free FLASH cells
