02:14:12
##forth
<cleobuline>
reveillez vous !
02:55:28
##forth
<xentrac>
veltas: maybe it could be a block-sized buffer in memory that isn't itself a block
03:34:58
##forth
<detritus>
hello
13:59:40
##forth
<cleobuline>
forthBot: LOAD ini.fth
13:59:41
##forth
<forthBot>
File ini.fth with MOON loaded
13:59:45
##forth
<cleobuline>
forth: 2000000 SQRT 1000 /MOD .S
13:59:54
##forth
<cleobuline>
forthBot: 2000000 SQRT 1000 /MOD .S
13:59:54
##forth
<forthBot>
<2> 414 1
14:02:05
##forth
<cleobuline>
forthBot: 3000000 SQRT 1000 /MOD .S
14:02:06
##forth
<forthBot>
<4> 414 1 732 1
15:35:31
##forth
<kpn>
It's cool that some Forths support Dijkstra's loop. You don't appreciate it until your implementation of use doesn't have it.
16:02:06
##forth
<forthBot>
Environment for cleobuline inactive, freeing...
16:15:49
##forth
<xentrac>
what, you mean like the nondeterministic guarded-commands langauge do ... od?
16:15:55
##forth
<xentrac>
not familiar with any such Forth
19:47:50
##forth
<kpn>
I'm talking the use of multiple "while"s in one "begin" "repeat" construct.
19:48:11
##forth
<kpn>
Same idea, different syntax.
19:50:02
##forth
<kpn>
gForth supports that, thugh there's a catch.
20:04:01
##forth
<xentrac>
hmm, I don't think that's the same idea; it's not nondeterministic, for one, and it doesn't have different loop bodies corresponding to the different conditions, for another
20:04:24
##forth
<xentrac>
(I've been trying to work through A Discipline of Programming with a friend lately)
20:18:04
##forth
<kpn>
I'm surprised to encounter someone else reading it. I gave up on chapter 2 ...
20:29:06
##forth
<kpn>
I see what you mean, it was wrong of me to call it Dijkstra's loop.