amforth-devel — Development discussion and user support

Re: [Amforth] Interrupts - T flag, asm float problem

[Matthias T. <mt...@we...>]

Hi Pito,

> I need the Status Register as well, of course (;-)).
> It cannot be changed during an interrupt event (you are manipulating
> the T flag there).

That is part of the magic how the forth VM synchronizes interrupt
handling with the controller state. Its not a convential way, yes.

> Imagine you run a routine and somebody changes a
> flag there in SR.

No problem. Remember: amforth is a runtime environment for
forth code, not for (huge) assembler code snippets. They
are useful, no doubt, but they must follow the rules
(expressed and implied ones).

> Would it be possible to use, as the interrupt
> signalling, a bit outside the status register??P.

Not really. There is nothing as speedy as the status
register based jumps. And the inner interpreter checks
that interrupt signalling bit every time it is called.
Speed is a must-have there.

What about you? Why do you not change the code to use
something else? e.g. some empty/ununsed/pushed register?
floating point division is not well known for speed, regardless
of the implementation.....

You could even disable interrupts during your assembly code, thats
not really a smart solution but it will prevent collisions.

Matthias

Re: [Amforth] Interrupts - T flag, asm float problem

[pito <pi...@vo...>]

I need the Status Register as well, of course (;-)).
It cannot be changed during an interrupt event (you are manipulating
the T flag there). Imagine you run a routine and somebody changes a
flag there in SR. Would it be possible to use, as the interrupt
signalling, a bit outside the status register??P.

----- PŮVODNÍ ZPRÁVA -----
Od: "Matthias Trute" <mt...@we...>
Komu: amf...@li...
Předmět: Re: [Amforth] Interrupts - T flag, asm float problem
Datum: 26.5.2011 - 20:22:38

> Hi Pito,
> 
> > Hi, it seems the T flag is currently used in a
> > much more "aggresive
> > > way".
> 
> Not at all. The usage of the T-Flag for dealing
> with
> interrupts is part of the code for a very long
> time
> (versions around 0.9). It is even documented since
> ever ;)
> What's new, is that there is now an example for
> the
> interrupts..
> 
> > The .asm floating routines are using T flag
> > within sign
> > > manipulation and when using timer (tick timer)
> > and the float calcs
> > > it does crash (e.g. do _float_asm_calc_ loop
> > never finishes).
> > > Q: when running a word e.g. f* written entirely
> > in asm. - what needs
> > > to be done? (1st option - not to use T flag, 2nd
> > one??) P.
> > 
> 1st Options is yours. All of the CPU is mine, with
> the
> (documented) exception of the temp registers. They
> can be
> used without restriction, but they are not kept
> between
> two words however.
> 
> Matthias
> 
> ------------------------------------------------------------------------------
> > vRanger cuts backup time in half-while increasing
> security.
> With the market-leading solution for virtual
> backup and recovery, 
> you get blazing-fast, flexible, and affordable
> data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 


-- 
IHNED.cz je nový, přehlednější a rychlejší. Přesvědčte se na:
www.ihned.cz

Re: [Amforth] Interrupts - T flag, asm float problem

[pito <pi...@vo...>]

I did not experienced such behaviour in 4.0 or 4.2. As you can
remember I did time measurements in a loop with ticktimer of most of
the asm floating primitives. No issues at that time. Now, when I
switch +timer it crashes. E.g.

> : test5 10000 0 do 123 s>f 123 s>f f* fdrop loop ;
ok
> test5
ok
> +timer
ok
> test5
CRASH

This worked with 4.0. P.


----- PŮVODNÍ ZPRÁVA -----
Od: "Matthias Trute" <mt...@we...>
Komu: amf...@li...
Předmět: Re: [Amforth] Interrupts - T flag, asm float problem
Datum: 26.5.2011 - 20:22:38

> Hi Pito,
> 
> > Hi, it seems the T flag is currently used in a
> > much more "aggresive
> > > way".
> 
> Not at all. The usage of the T-Flag for dealing
> with
> interrupts is part of the code for a very long
> time
> (versions around 0.9). It is even documented since
> ever ;)
> What's new, is that there is now an example for
> the
> interrupts..
> 
> > The .asm floating routines are using T flag
> > within sign
> > > manipulation and when using timer (tick timer)
> > and the float calcs
> > > it does crash (e.g. do _float_asm_calc_ loop
> > never finishes).
> > > Q: when running a word e.g. f* written entirely
> > in asm. - what needs
> > > to be done? (1st option - not to use T flag, 2nd
> > one??) P.
> > 
> 1st Options is yours. All of the CPU is mine, with
> the
> (documented) exception of the temp registers. They
> can be
> used without restriction, but they are not kept
> between
> two words however.
> 
> Matthias
> 
> ------------------------------------------------------------------------------
> > vRanger cuts backup time in half-while increasing
> security.
> With the market-leading solution for virtual
> backup and recovery, 
> you get blazing-fast, flexible, and affordable
> data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

Re: [Amforth] Interrupts - T flag, asm float problem

[Matthias T. <mt...@we...>]

Hi Pito,

> Hi, it seems the T flag is currently used in a much more "aggresive
> way".

Not at all. The usage of the T-Flag for dealing with
interrupts is part of the code for a very long time
(versions around 0.9). It is even documented since ever ;)
What's new, is that there is now an example for the
interrupts..

> The .asm floating routines are using T flag within sign
> manipulation and when using timer (tick timer) and the float calcs
> it does crash (e.g. do _float_asm_calc_ loop never finishes).
> Q: when running a word e.g. f* written entirely in asm. - what needs
> to be done? (1st option - not to use T flag, 2nd one??) P.

1st Options is yours. All of the CPU is mine, with the
(documented) exception of the temp registers. They can be
used without restriction, but they are not kept between
two words however.

Matthias

[Amforth] Interrupts - T flag, asm float problem

[pito <pi...@vo...>]

Hi, it seems the T flag is currently used in a much more "aggresive
way". The .asm floating routines are using T flag within sign
manipulation and when using timer (tick timer) and the float calcs
it does crash (e.g. do _float_asm_calc_ loop never finishes).
Q: when running a word e.g. f* written entirely in asm. - what needs
to be done? (1st option - not to use T flag, 2nd one??) P.

Re: [Amforth] Release 4.4 tagged and published

[Leon N. M. <leo...@gm...>]

On Tuesday, May 24, 2011 07:54:08 PM Matthias Trute wrote:
> - The recognizer thing is now documented (to some degree);
>   I sent an article to the German Forth FIG about it, that
>   should be translated into plain English ASAP. Leons floating
>   point library (a few patches are needed to work with it, just
>   use the float.frt that is included) can now be included at
>   runtime and the text interpreter can deal afterwards with
>   the numbers nativly. Great stuff.

Nice! I haven't played around with the floating point code (or amforth in general) in a while, but I'll try to make some time with it this weekend. It looks like some of the bugs are old ones 
from my code (e.g. >float failing for numbers with too many digits), so I'll see what I can do.

-Leon

Re: [Amforth] Recognizer - float - issue

[pito <pi...@vo...>]

Hmmm, however it does not work when compiled:

> : test7 9.33e-1 8.334e+12 f* fp. ;
ok
> test7
3.402823E38  ok
> 9.33e-1 8.334e+12 f* fp. 
7.775622E12  ok
> 

Any hint from experts?? P.




----- PŮVODNÍ ZPRÁVA -----
Od: "pito" <pi...@vo...>
Komu: amf...@li...
Předmět: [Amforth] Recognizer - float - issue
Datum: 26.5.2011 - 14:34:07

> Hi - this does work with my setup:
> > marker -mycode
> ok
> > : rec-float count >float state @ if postpone
> > fliteral then ;
> > ok
> > .s
> ok
> > get-recognizer
> ok
> > .s
> 0 2005 3 
> 1 2007 1562 
> 2 2009 1532 
> 3 2011 1593 
> ok
> > : place-rec ( xt -- )
> okget-recognizer
> okdup >r
> ok1-  n>r
> okswap
> oknr> drop r> 1+
> okset-recognizer
> ok;
> ok
> > get-recognizer
> ok
> > .s
> 0 1997 3 
> 1 1999 1562 
> 2 2001 1532 
> 3 2003 1593 
> 4 2005 3 
> 5 2007 1562 
> 6 2009 1532 
> 7 2011 1593 
> ok
> > ...
> ... ?? -13 4 
> > ' rec-float place-rec
> ok
> > .s
> ok
> > get-recognizer
> ok
> > .s
> 0 2003 4 
> 1 2005 1562 
> 2 2007 1532 
> 3 2009 8483 
> 4 2011 1593 
> ok
> > 1.222e6 fs.
> 1.2219999E6  ok
> > -3.556e12 0.564343E-12 f* fp.
> -2.006803  ok
> > 1.00 fsin fs.
> 8.414711E-1  ok
> > 1.000e15 flog10 fs.
> 1.50000024E1  ok
> >
> 
> 
> ------------------------------------------------------------------------------
> > vRanger cuts backup time in half-while increasing
> security.
> With the market-leading solution for virtual
> backup and recovery, 
> you get blazing-fast, flexible, and affordable
> data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

[Amforth] Recognizer - float - issue

[pito <pi...@vo...>]

Hi - this does work with my setup:
> marker -mycode
ok
> : rec-float count >float state @ if postpone fliteral then ;
ok
> .s
ok
> get-recognizer
ok
> .s
0 2005 3 
1 2007 1562 
2 2009 1532 
3 2011 1593 
ok
> : place-rec ( xt -- )
okget-recognizer
okdup >r
ok1-  n>r
okswap
oknr> drop r> 1+
okset-recognizer
ok;
ok
> get-recognizer
ok
> .s
0 1997 3 
1 1999 1562 
2 2001 1532 
3 2003 1593 
4 2005 3 
5 2007 1562 
6 2009 1532 
7 2011 1593 
ok
> ...
... ?? -13 4 
> ' rec-float place-rec
ok
> .s
ok
> get-recognizer
ok
> .s
0 2003 4 
1 2005 1562 
2 2007 1532 
3 2009 8483 
4 2011 1593 
ok
> 1.222e6 fs.
1.2219999E6  ok
> -3.556e12 0.564343E-12 f* fp.
-2.006803  ok
> 1.00 fsin fs.
8.414711E-1  ok
> 1.000e15 flog10 fs.
1.50000024E1  ok
>

[Amforth] Bug - >float or fsn.

[pito <pi...@vo...>]

Hi, this is when we enter a little bit more decimal places -
probably a bug in >float or fsn.:

\ floating point input with >float, "& 1.23456e12"
: # bl word count >float not abort" NaN" 
state @ if postpone fliteral then ; immediate

\ print 6 decimal places
: fp. 6 fsn. ;


> # 3.141592 fp.
3.141592  ok
> # 3.1415926 fp.
3.141592  ok
> # 3.14159265 fp.
3.141592  ok
> # 3.141592653 fp.
3.141592E-1  ok
> # 3.14159265366 fp.
3.141592E-3  ok
> 

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

for time beeing this still works with 4.4:

> : # bl word count >float not abort" NaN" 
okstate @ if postpone fliteral then ; immediate
ok
> # 3.444e6 fs.
3.4439998E6  ok
> # 1.234e6 fs.
1.23399997E6  ok
> # 123456789e10 fs.
1.23456776E18  ok
> # -1.3343e-12 # 6.222E22 f* fs.
-8.3020134E10  ok
> # 3.44W-1
NaN
> 

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

Erich thanks,
yes I did, indeed. Therefore it could have been be compiled, however
still coping with rec-float and place-rec.

Spent ~5h to migrate from 4.0, still did not print any float..

----- PŮVODNÍ ZPRÁVA -----
Od: "Erich Waelde" <ew....@na...>
Komu: "Everything around amforth"
<amf...@li...>
Předmět: Re: [Amforth] Amforth 4.4. - issues
Datum: 25.5.2011 - 22:15:52

> Hi Pito,
> 
> On 05/25/2011 09:36 PM, pito wrote:
> > When put into dict_appl.inc:
> >
> > C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_to_r.asm(23):
> > > > > error: Relative branch out of reach
> > C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\dict_appl.inc(6):
> > > > > info:
> > 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_to_r.asm'
> > > > > included from here
> > C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\amforth.asm(14):
> > > > > info:
> > 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\dict_appl.inc'
> > > > > included from here
> > C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\template.asm(52):
> > > > > info:
> > 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\amforth.asm'
> > > included from here
> > C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_r_from.asm(23):
> > > > > error: Relative branch out of reach
> 
> Assuming that n_r_from.asm is causing the error,
> add this file
> to dict_appl_core.inc instead of dict_appl.inc.
> This makes the
> work come earlier in the code layout. If that
> doesn't help,
> change
> rjmp DO_NEXT
> to
> jmp_ DO_NEXT
> which will use a bigger address range.
> 
> Cheers,
> Erich
> 
> 
> ------------------------------------------------------------------------------
> > vRanger cuts backup time in half-while increasing
> security.
> With the market-leading solution for virtual
> backup and recovery, 
> you get blazing-fast, flexible, and affordable
> data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 


-- 
IHNED.cz je nový, přehlednější a rychlejší. Přesvědčte se na:
www.ihned.cz

Re: [Amforth] Amforth 4.4. - issues

[Erich W. <ew....@na...>]

Hi Pito,

On 05/25/2011 09:36 PM, pito wrote:
> When put into dict_appl.inc:
>
> C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_to_r.asm(23):
> error: Relative branch out of reach
> C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\dict_appl.inc(6):
> info:
> 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_to_r.asm'
> included from here
> C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\amforth.asm(14):
> info:
> 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\dict_appl.inc'
> included from here
> C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\template.asm(52):
> info: 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\amforth.asm'
> included from here
> C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_r_from.asm(23):
> error: Relative branch out of reach

Assuming that n_r_from.asm is causing the error, add this file
to dict_appl_core.inc instead of dict_appl.inc. This makes the
work come earlier in the code layout. If that doesn't help,
change
   rjmp DO_NEXT
to
   jmp_ DO_NEXT
which will use a bigger address range.

Cheers,
Erich

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

> .s
ok
> marker -fmathrec
ok
> .s
ok
> : rec-float count >float
okif state @ if  postpone fliteral  then -1
okelse 0
ok;
ok
> .s
0 2011 8399 
ok
> 

There is an issue with the rec-float..P.

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

When put into dict_appl.inc:

C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_to_r.asm(23):
error: Relative branch out of reach
C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\dict_appl.inc(6):
info:
'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_to_r.asm'
included from here
C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\amforth.asm(14):
info:
'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\dict_appl.inc'
included from here
C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\appl\template44_32\template.asm(52):
info: 'C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\amforth.asm'
included from here
C:\MyCode\AVR\WINAVR\projects\AMFORTH\my_44\core\words/n_r_from.asm(23):
error: Relative branch out of reach


----- PŮVODNÍ ZPRÁVA -----
Od: "pito" <pi...@vo...>
Komu: mt...@we..., pi...@vo...,
amf...@li...
Předmět: Re: [Amforth] Amforth 4.4. - issues
Datum: 25.5.2011 - 20:42:15

> ..a pity it shots down amforth so I have to
> reload- 
> 
> > : place-rec ( xt -- )
> ok    get-recognizer
> ok    dup >r
> ok    1-  n>r
> n>r ?? -13 12
> >     swap
> ok
> >     nr> drop r> 1+
> nr> ?? -13 8
> >     set-recogniz
> 
> BAANGGG
> 
> 
> > 
> > use a word place-rec as a helper word.
> > 
> > : place-rec ( xt -- )
> > get-recognizer
> > dup >r
> > 1-  n>r
> > swap
> > nr> drop r> 1+
> > set-recognizer
> > ;
> > 
> > and have a look at the following session log
> > 
> > 
> > > 123e4 fs.
> > 123e4 ?? -13 6
> > > ' rec-float place-rec
> > ok
> > > 123e4 fs.
> > 1.2299999E6 ok
> > >
> > 
> > HTH
> > Matthias
> > 
> 
> 

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

I added the missing words to dict_appl_core.inc (otherwise I got an
error like branch too far or something like that):

.include "dict_core.inc"
.include "words/store-e.asm"
.include "words/fetch-e.asm"

.include "words/store-i.asm"
.include "words/store-i_nrww.asm"
.include "words/fetch-i.asm"

.include "words/n_to_r.asm"
.include "words/n_r_from.asm"

_______________________________

After compilation, upload of everything needed ( I hope so):

>  ' rec-float place-rec
ok
> 1.222e-23 4.556e12 f* fs.
amforth 4.4 ATmega32
> 
ok
> 4.555e2 fs.
amforth 4.4 ATmega32
> 123e4 fs.
amforth 4.4 ATmega32
> 
ok

p.


----- PŮVODNÍ ZPRÁVA -----
Od: "pito" <pi...@vo...>
Komu: mt...@we..., pi...@vo...,
amf...@li...
Předmět: Re: [Amforth] Amforth 4.4. - issues
Datum: 25.5.2011 - 20:42:15

> ..a pity it shots down amforth so I have to
> reload- 
> 
> > : place-rec ( xt -- )
> ok    get-recognizer
> ok    dup >r
> ok    1-  n>r
> n>r ?? -13 12
> >     swap
> ok
> >     nr> drop r> 1+
> nr> ?? -13 8
> >     set-recogniz
> 
> BAANGGG
> 
> 
> > 
> > use a word place-rec as a helper word.
> > 
> > : place-rec ( xt -- )
> > get-recognizer
> > dup >r
> > 1-  n>r
> > swap
> > nr> drop r> 1+
> > set-recognizer
> > ;
> > 
> > and have a look at the following session log
> > 
> > 
> > > 123e4 fs.
> > 123e4 ?? -13 6
> > > ' rec-float place-rec
> > ok
> > > 123e4 fs.
> > 1.2299999E6 ok
> > >
> > 
> > HTH
> > Matthias
> > 
> 
> 


-- 
IHNED.cz je nový, přehlednější a rychlejší. Přesvědčte se na:
www.ihned.cz

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

..a pity it shots down amforth so I have to reload- 

> : place-rec ( xt -- )
ok    get-recognizer
ok    dup >r
ok    1-  n>r
n>r ?? -13 12
>     swap
ok
>     nr> drop r> 1+
nr> ?? -13 8
>     set-recogniz

BAANGGG


> 
> use a word place-rec as a helper word.
> 
> : place-rec ( xt -- )
> get-recognizer
> dup >r
> 1-  n>r
> swap
> nr> drop r> 1+
> set-recognizer
> ;
> 
> and have a look at the following session log
> 
> 
> > 123e4 fs.
> 123e4 ?? -13 6
> > ' rec-float place-rec
> ok
> > 123e4 fs.
> 1.2299999E6 ok
> >
> 
> HTH
> Matthias
> 

Re: [Amforth] Amforth 4.4. - issues

[Matthias T. <mt...@we...>]

Hi Pito,

> Thanks, now it compiles!
> My feeling is I have to add the rec-float to the recognizer's list.
> How to?

http://amforth.sourceforge.net/amforth.pdf

in short:

use a word place-rec as a helper word.

: place-rec ( xt -- )
    get-recognizer
    dup >r
    1-  n>r
    swap
    nr> drop r> 1+
    set-recognizer
;

and have a look at the following session log


> 123e4 fs.
123e4 ?? -13 6
> ' rec-float place-rec
ok
> 123e4 fs.
1.2299999E6 ok
>

HTH
Matthias

Re: [Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

Thanks, now it compiles!
My feeling is I have to add the rec-float to the recognizer's list.
How to?
P.

> >> : rec-float count >float
> > ok   if state @ if fliteral then -1
> > ?? -42 31
> 
> -42 means stack underflow, just add a postpone in
> front of fliteral. I'll add the fix later to the



-- 
IHNED.cz je nový, přehlednější a rychlejší. Přesvědčte se na:
www.ihned.cz

Re: [Amforth] Release 4.4 tagged and published

[Matthias T. <mt...@we...>]

Pito,

> Does it mean we can input the float now like this?:
> 
> -3.44556e-16 0.23233E13 f* fs.

yes, that is the goal of it. You can even compile
floats in colon definitions and they will work.


> Is the Leon's float patched in the 4.4 already? (as I can remember
> there was an issue with printing the floats with 4.2, it worked with
> 4.0)

yeah, there were a few regressions there. Now it works again. see my
other mail.

Matthias

Re: [Amforth] Migration 4.0 to 4.4.

[Matthias T. <mt...@we...>]

Pito,

> Is there any recommendation on migration from 4.0 to 4.4? P.

The general rule is: check the changelog on the website.
There I (try to) document any changes that I think may
be important.  If in doubt for any particular word, just
check the svn repository. Every commit has a log entry as
well. A commit may affect more than one file, that may
be useful as well.


Matthias

Re: [Amforth] Amforth 4.4. - issues

[Matthias T. <mt...@we...>]

Hi Pito,


>> : rec-float count >float
> ok   if state @ if fliteral then -1
> ?? -42 31

-42 means stack underflow, just add a postpone in
front of fliteral. I'll add the fix later to the code
base.

Thanks for reporting
Matthias

[Amforth] Amforth 4.4. - issues

[pito <pi...@vo...>]

Hi, I am trying to migrate from 4.0 - these are the first issues
I've encountered - maybe it saves few minutes to the others:

1. qeens and life need pick.asm, ms.asm, udotr.asm included (or
frts)
2. I am getting an error here (float lib's last word ;( ):

> \ recognizer is a feature that is available for amforth 4.3 and up
ok
> : rec-float count >float
ok   if state @ if fliteral then -1
?? -42 31
>    else 0
ok
> ;

-p


-- 
IHNED.cz je nový, přehlednější a rychlejší. Přesvědčte se na:
www.ihned.cz

Re: [Amforth] Release 4.4 tagged and published

[<an...@ki...>]

Excellent, thanks guys.

Hopefully I will get some time to give it a spin over the nexy couple of
weeks.

Think I will stick with case sensitive.

Cheers

Andy Kirby

On 24/05/11 18:54, Matthias Trute wrote:
> Hi,
> 
> I've just tagged and published a new release named 4.4.
> 
> Noteworthy changes are
> 
> - The Game of Life with terminal output (requires controllers
>   with at least many KB RAM, otherwise make the world small
>   enough). A queens puzzle solver as well (more kind of a
>   benchmark however).
> 
> - The reference card got a more compact layout, many bugs
>   from the documentation headers in the source file are gone.
> 
> - new interrupt handling. The ideas are relativly old but
>   now it works well. Many thanks to Wojciech and Al, I beg
>   your pardon that it took such a long time to implement. But
>   sometimes some active tests such as Erichs will speed up
>   things ;=)
> 
> - The recognizer thing is now documented (to some degree);
>   I sent an article to the German Forth FIG about it, that
>   should be translated into plain English ASAP. Leons floating
>   point library (a few patches are needed to work with it, just
>   use the float.frt that is included) can now be included at
>   runtime and the text interpreter can deal afterwards with
>   the numbers nativly. Great stuff.
> 
> - internally there are even more source files and the
>   amforth.asm file got smaller than ever. COLD is now
>   WARM and the new COLD is what was in amforth.asm...
> 
> - not really my favorite: If you set WANT_IGNORECASE to
>   1 and rebuild amforth you get a case insensive dictionary
>   lookup. It took a few lines of code in icompare.asm, The
>   discussion about it took more time than the implementation. Brr
> 
> Have fun, esp with Life
> 
> Matthias
> 
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery, 
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 

[Amforth] Migration 4.0 to 4.4.

[pito <pi...@vo...>]

Is there any recommendation on migration from 4.0 to 4.4? P.

Re: [Amforth] Release 4.4 tagged and published

[pito <pi...@vo...>]

Matthias, great news!

> afterwards with the numbers nativly. Great stuff.

Last fall I did it like:

\ floating point input with >float, "& 1.23456e12"
: & bl word count >float not abort" NaN" 
state @ if postpone fliteral then ; immediate

& -3.44556e-16 & 0.23233E13 f* fs.

Does it mean we can input the float now like this?:

-3.44556e-16 0.23233E13 f* fs.

Is the Leon's float patched in the 4.4 already? (as I can remember
there was an issue with printing the floats with 4.2, it worked with
4.0)

> It took a few lines of code in icompare.asm, The
> discussion about it took more time than the implementation. Brr
Who needs that actually?

Pito.


-- 
IHNED.cz je nový, přehlednější a rychlejší. Přesvědčte se na:
www.ihned.cz