01:06:28
##forth
<xentrac>
veltas: haha
01:07:48
##forth
<xentrac>
and I suppose 1 dup + dup + 1+ dup + base ! will set the I/O base to decimal regardless of the initial base
01:09:58
##forth
<xentrac>
crc: 23:09 <xentrac> 3 4 + .
01:09:58
##forth
<xentrac>
23:09 <[bot]konilo> Error running ilo: [Errno 2] No such file or directory:
01:10:52
##forth
<crc>
Hmm, I'll check things
01:11:03
##forth
<xentrac>
not important but I thought you might want to know
01:12:50
##forth
<crc>
(incidentally, that wouldn't actually work in konilo; the equivilent would be `#3 #4 n:add n:put`)
01:18:59
##forth
<xentrac>
ah, thanks
01:25:17
##forth
<[bot]konilo>
Konilo via IRC
01:25:46
##forth
<MrMobius>
2 base ! 1010 base !
01:28:04
##forth
<crc>
xentrac: fixed some path issues; it should be working now
06:28:31
##forth
<szilard>
Did anybody managed to compile recent gforth (>0.7.9) at all? It just hangs here during the compilation on my machines/phones.
09:49:06
##forth
<anthk_>
szilard: on i686 the gforth port it's broken under OpenBSD; it might be the same upstream
09:49:41
##forth
<anthk_>
I'm using pforth and is not bad for an ans implementation; altough IDK how to use the sockets module
09:53:28
##forth
<szilard>
anthk_ thanks!
10:42:07
##forth
<anthk_>
It lacks gnu forth's extra modules but overall as a forth it's good
11:14:18
##forth
<szilard>
I just compiled PForth on OmniOS (it is an Illumos variant / distribution. Illumos itself is a fork of OpenSolaris, which is Net/Consolidation, eg. the basis of Sun Solaris 10).
12:52:32
##forth
<KipIngram>
anthk_: MANY years ago I did some work with pforth and used sockets. I tweaked it so that the input stream arrived via a socket. I used it to run a pick and place machine.
13:59:48
##forth
<xentrac>
is pForth derived from PFE, anthk_?
14:08:58
##forth
<KipIngram>
xentrac: I don't think so; their histories online seem to indicate they're separate efforts.
14:10:52
##forth
<KipIngram>
Both started in the early 1990s, but different people are attached. And it looks like pForth was an attempt to be more minimalist. Of course I guess there's no way to know all of the influences a developer may have had (unless they tell us).
14:17:51
##forth
<crc>
iirc, pfe is slightly older than pforth, and the two aren't related
14:35:03
##forth
<KipIngram>
pforth appealed to me for my purposes at the time I used it (early 2000's) because it's so very portable. It just gave me no trouble at all with compiling.
14:37:10
##forth
<KipIngram>
The main fuss I had with it was getting just the basic prompt operation the way I wanted it - I wanted the usual, with the output and the "ok" on the same line as my input. I didn't realize then how deeply that was baked into the line input built-ins. I fixed that after switching the input stream over to a socket, so I didn't actually have to putz around with termios that time.
14:38:29
##forth
<xentrac>
KipIngram: aha, I was confused by anthk_ seeming to lump them together
14:39:11
##forth
<xentrac>
I recently took the time to hack the first version of PFE to compile on current Linux
14:39:53
##forth
<xentrac>
it used a bunch of GCC extensions to C that have since been removed, and even a Linux system call that has been removed
14:41:04
##forth
<xentrac>
more recent versions of PFE compile out of the box, but I wanted to know if my "minimal roguelike" hack would run under the first version of PFE, because that was the version that ran under MS-DOG
14:42:09
##forth
<cleobuline>
forthBot: LOAD "test.fth"
14:42:16
##forth
<cleobuline>
forthBot: LOAD "test2.fth"
14:42:27
##forth
<cleobuline>
forthBot: MACRON
14:42:28
##forth
<forthBot>
Macron est un saint homme !
15:16:21
##forth
<cleobuline>
forthBot: TODAY-CAL-IRC
15:16:21
##forth
<forthBot>
April 2025
15:16:22
##forth
<forthBot>
1 2 3 4 5 6
15:16:22
##forth
<forthBot>
7 8 9 10 11 12 13
15:16:22
##forth
<forthBot>
14 15 16 17 18 19 20
15:16:23
##forth
<forthBot>
21 22 23 24 25 26 27
15:16:23
##forth
<forthBot>
28 29 30
15:16:24
##forth
<forthBot>
Mo Tu We Th Fr Sa Su
15:18:27
##forth
<qbit>
ah, good old ^V day
15:35:36
##forth
<cleobuline>
forthBot: TODAY-CAL-IRC
15:35:36
##forth
<forthBot>
April 2025
15:35:36
##forth
<forthBot>
1 2 3 4 5 6
15:35:37
##forth
<forthBot>
7 8 9 10 11 12 13
15:35:37
##forth
<forthBot>
14 15 16 17 18 19 20
15:35:38
##forth
<forthBot>
21 22 23 24 25 26 27
15:35:38
##forth
<forthBot>
28 29 30
15:35:38
##forth
<forthBot>
Mo Tu We Th Fr Sa Su
15:36:07
##forth
<cleobuline>
strange the days are in the bottom :(
15:37:54
##forth
<xentrac>
FIFO
15:37:56
##forth
<xentrac>
LIFO
15:39:25
##forth
<cleobuline>
forthBot: SEE CAL-IRC-HIGHLIGHT
15:39:25
##forth
<forthBot>
: CAL-IRC-HIGHLIGHT 2 PICK TODAY-DAY ! 2DUP SWAP MONTH-NAME DROP 32 EMIT NUM-TO-STR CR ." Mo Tu We Th Fr Sa Su " CR 2DUP ZELLER DUP 0 = IF DROP 6 ELSE 1 - THEN DUP OFF ! OFF @ 0 > IF OFF @ 0 DO 32 EMIT 32 EMIT 32 EMIT LOOP THEN DROP 2DUP 2DUP DAYS-IN-MONTH 1 + 1 DO I 10 < IF 32 EMIT 32 EMIT ELSE 32 EMIT THEN I TODAY-DAY @ = IF 22 EMIT I NUM-TO-STR 15 EMIT ELSE I NUM-TO-STR THEN OFF @ I + 7 MOD 0
15:39:25
##forth
<forthBot>
= IF CR THEN LOOP 2DROP 2DROP 2DROP CR ;
15:39:51
##forth
<cleobuline>
they should be at the top
15:40:52
##forth
<qbit>
neat, is the code for forthBot available anywhere?
15:44:09
##forth
<cleobuline>
forthBot: CREDIT
15:44:35
##forth
<cleobuline>
there is a release use at your own risk :)
15:44:56
##forth
<cleobuline>
run on macos ubuntu and others
15:45:17
##forth
<cleobuline>
not windows
15:56:58
##forth
* KipIngram likes "not windows." ;-)
15:58:19
##forth
<qbit>
ty :D
16:00:51
##forth
<cleobuline>
windows is obsolete
16:01:07
##forth
<cleobuline>
nothing with unix
17:44:09
##forth
<forthBot>
Environment for cleobuline inactive, freeing...
18:54:18
##forth
<anthk_>
forthBot: here @
18:54:18
##forth
<forthBot>
Unknown word: here
18:54:18
##forth
<forthBot>
Error: FETCH: Stack underflow for address
20:54:18
##forth
<forthBot>
Environment for anthk_ inactive, freeing...