<joe9>
the first 4 chapters are useful. but, beyond that, I am not sure how relevant it is now.
<lispmacs[work]>
I have bookmarked these
jedb_ is now known as jedb
dave0 has quit [Quit: dave's not here]
lispmacs[work] has quit [Ping timeout: 268 seconds]
sts-q has quit [Remote host closed the connection]
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
lispmacs[work] has joined #forth
Gromboli has quit [Quit: Leaving]
<proteus-guy>
joe9, Brad Rodriguez works are always relevant in terms of implementation considerations. Of course those are old CPUs so not directly applicable but the thought processes are absolutely still good.
jedb_ has joined #forth
jedb has quit [Ping timeout: 264 seconds]
jedb__ has joined #forth
jedb_ has quit [Ping timeout: 256 seconds]
jedb__ is now known as jedb
gravicappa has joined #forth
X-Scale` has joined #forth
X-Scale has quit [Ping timeout: 260 seconds]
X-Scale` is now known as X-Scale
sts-q has joined #forth
<lispmacs>
I'm a little confused by double precision numbers. In gforth:
<lispmacs>
0 1 1 0 d- .s <2> -1 0 ok
<lispmacs>
shouldn't the results be some large number followed by 0?
<lispmacs>
.s
<lispmacs>
oops, wrong window
<lispmacs>
this is a little confusing too:
<lispmacs>
-1 0 dabs .s <2> -1 0 ok
<lispmacs>
.s
hosewiejacke has joined #forth
<DKordic>
IIRC ""Double"" number is ""Digit Carry ( ToS )"".
jedb_ has joined #forth
jedb has quit [Ping timeout: 272 seconds]
xek has joined #forth
<inode>
lispmacs: .S might not be aware of the representation you'd like to see those numbers in. tried looking at them with D. (or UD.)?
xek has quit [Ping timeout: 264 seconds]
jedb_ has quit [Ping timeout: 256 seconds]
jedb has joined #forth
hosewiejacke has quit [Ping timeout: 240 seconds]
proteusguy has quit [Ping timeout: 268 seconds]
proteus-guy has quit [Ping timeout: 272 seconds]
joe9 has quit [Ping timeout: 265 seconds]
joe9 has joined #forth
proteus-guy has joined #forth
proteusguy has joined #forth
xek has joined #forth
dave0 has joined #forth
dave0 has quit [Quit: dave's not here]
<lispmacs>
inode: in gforth, `d.s' seems to provide the expected results for
<lispmacs>
seems to display as unsigned number. but why have a `dabs' word for an unsigned number?
<lispmacs>
`d.s' does not appear to be documented in gforth, and `ud.s' does not seem to exist
Gromboli has joined #forth
<inode>
DABS is only looking at the most significant half of the double, it's only performing negation (DNEGATE) if that half is less than 0 (SEE DABS)
xek has quit [Ping timeout: 264 seconds]
xek has joined #forth
xek has quit [Ping timeout: 256 seconds]
<veltas>
lispmacs: -1 is expected, it's the maximum unsigned value, which is what I expect to see in the less significant cell after subtracting 1 from '0 1'
<veltas>
In a double number the less significant cell would not have sign info
<veltas>
In increasing order: -2 0 -1 0 0 1 1 1 2 1 etc.
gravicappa has quit [Ping timeout: 240 seconds]
<lispmacs>
inode: veltas: okay, thanks, it is making a little more sense now
gravicappa has joined #forth
gravicappa has quit [Read error: Connection reset by peer]
gravicappa has joined #forth
lispmacs[work] has quit [Ping timeout: 272 seconds]
xek has joined #forth
lispmacs[work] has joined #forth
lispmacs[work] has quit [Ping timeout: 240 seconds]
lispmacs[work] has joined #forth
Gromboli has quit [Ping timeout: 258 seconds]
Gromboli has joined #forth
Gromboli has quit [Quit: Leaving]
gravicappa has quit [Ping timeout: 265 seconds]
lispmacs[work] has quit [Ping timeout: 246 seconds]
lispmacs[work] has joined #forth
xek has quit [Ping timeout: 240 seconds]
lispmacs[work] has quit [Ping timeout: 246 seconds]