hosewiejacke2 has quit [Ping timeout: 246 seconds]
X-Scale has joined #forth
f-a has quit [Ping timeout: 252 seconds]
gravicappa has quit [Ping timeout: 240 seconds]
f-a has joined #forth
gravicappa has joined #forth
rpcope has quit [Ping timeout: 252 seconds]
dave0 has quit [Quit: dave's not here]
hosewiejacke2 has joined #forth
rpcope has joined #forth
hosewiejacke2 has quit [Ping timeout: 240 seconds]
tech_exorcist has joined #forth
rpcope has quit [Ping timeout: 252 seconds]
rpcope has joined #forth
f-a has quit [Quit: leaving]
<KipIngram>
Yeah, I'm still a little tempted by the idea, but for the time being I'm let 'e' make the number floating point.
<KipIngram>
I can just picture myself, though, being smugly happy at just having to write 1e9 in a definition instead of the ten-character 1000000000
<KipIngram>
Given my fondness for short definitions. :-)
<KipIngram>
But then I'd have to decide whether to treat negative exponents with no . as an error or not. Treating it as an error would be a little more "pure" (i.e., the . being absolutely required), but on the other hand 1e-3 has a perfectly clear meaning.
<KipIngram>
Someone asked me about doubles the other day - it had occurred to me that I could let 'e' be the required item for floating point and then I could have doubles and floatingn point.
<KipIngram>
I'm just not accustomed to having scientific notation be *required* though - I don't totally like that vibe.
<KipIngram>
And finally the other thing that occurred to me was to have a clean point within the code where I have a "power of 10 floating point number," and then tack the use of the FPU to get a fully standard float on after that. Then I'd have a system that provided some sort of floating point support even in the absence of floating point hardware.
<KipIngram>
Make the FPU optional.
MrMobius has joined #forth
andrei-n has quit [Quit: Leaving]
f-a has joined #forth
Zarutian_HTC1 has joined #forth
Zarutian_HTC has quit [Read error: Connection reset by peer]
Zarutian_HTC has joined #forth
Zarutian_HTC1 has quit [Read error: Connection reset by peer]
<KipIngram>
Well, this section of composition of forms in the LISP 1.5 primer is a little opaque. I mean, I see exactly what they're wanting to get at, but the description is rather intricate - seems like it could have been made more clear. I'm not sure this would have "taught me" this material if I didn't already have a sense of what was coming. At least not without going through it extremely slowly and carefully.
hosewiejacke2 has joined #forth
shmorgle has joined #forth
f-a has quit [Read error: Connection reset by peer]
f-a has joined #forth
Zarutian_HTC has quit [Ping timeout: 252 seconds]
Zarutian_HTC has joined #forth
hosewiejacke2 has quit [Ping timeout: 240 seconds]
eli_oat has joined #forth
eli_oat has quit [Client Quit]
gravicappa has quit [Ping timeout: 240 seconds]
gravicappa has joined #forth
hosewiejacke2 has joined #forth
hosewiejacke2 has quit [Remote host closed the connection]
gravicappa has quit [Ping timeout: 246 seconds]
mtsd has quit [Ping timeout: 240 seconds]
f-a has quit [Read error: Connection reset by peer]
dave0 has joined #forth
<dave0>
maw
f-a has joined #forth
<KipIngram>
Afternoon.
tech_exorcist has quit [Ping timeout: 265 seconds]
Zarutian_HTC has quit [Remote host closed the connection]
f-a has quit [Quit: leaving]
Zarutian_HTC has joined #forth
Zarutian_HTC1 has joined #forth
Zarutian_HTC has quit [Read error: Connection reset by peer]