01:07:11
##forth
<cleobuline>
bon
01:08:33
##forth
<cleobuline>
macOsForth: : test DO I NUM-TO-STR LOOP CR ;
01:08:33
##forth
<macOsForth>
Unknown word in definition: NUM-TO-STR
01:08:33
##forth
<macOsForth>
Error: Definition discarded due to error
01:08:54
##forth
<cleobuline>
macOsForth: LOAD "test.fth"
01:09:03
##forth
<cleobuline>
macOsForth: LOAD "test2.fth"
01:09:06
##forth
<cleobuline>
macOsForth: : test DO I NUM-TO-STR LOOP CR ;
01:09:23
##forth
<cleobuline>
macOsForth: 10 0 test
01:09:23
##forth
<macOsForth>
0123456789
01:15:01
##forth
<cleobuline>
macOsForth: : test DO I -1 +LOOP ;
01:15:27
##forth
<cleobuline>
macOsForth: 0 10 test .S
01:15:28
##forth
<macOsForth>
<10> 10 9 8 7 6 5 4 3 2 1
01:19:09
##forth
<cleobuline>
everyone is sleeping ?
01:21:04
##forth
<cleobuline>
macOsForth: TODAY-CAL-IRC
01:21:04
##forth
<macOsForth>
April 2025
01:21:05
##forth
<macOsForth>
Mo Tu We Th Fr Sa Su
01:21:05
##forth
<macOsForth>
7 8 9 10 11 12 13
01:21:05
##forth
<macOsForth>
14 15 16 17 18 19 20
01:21:06
##forth
<macOsForth>
1 2 3 4 5 6
01:21:06
##forth
<macOsForth>
28 29 30
01:21:07
##forth
<macOsForth>
21 22 23 24 25 26 27
01:21:11
##forth
<cleobuline>
lol
01:22:14
##forth
<cleobuline>
macOsForth: TODAY .S `
01:22:14
##forth
<macOsForth>
<13> 10 9 8 7 6 5 4 3 2 1 30 4 2025
01:22:14
##forth
<macOsForth>
Unknown word: `
01:22:44
##forth
<cleobuline>
macOsForth: TODAY-CAL-IRC
01:22:44
##forth
<macOsForth>
April 2025
01:22:44
##forth
<macOsForth>
1 2 3 4 5 6
01:22:44
##forth
<macOsForth>
7 8 9 10 11 12 13
01:22:45
##forth
<macOsForth>
14 15 16 17 18 19 20
01:22:45
##forth
<macOsForth>
Mo Tu We Th Fr Sa Su
01:22:46
##forth
<macOsForth>
28 29 30
01:22:46
##forth
<macOsForth>
21 22 23 24 25 26 27
01:23:03
##forth
<cleobuline>
strange mixture ...
15:32:51
##forth
<vms14>
crc do you have any resources or advice for making a bytecode interpreter?
15:33:08
##forth
<vms14>
and a bytecode compiler
16:52:20
##forth
<KipIngram>
vms14: What language will you be working in?
17:20:43
##forth
<vms14_>
KipIngram the initial target language would be js and other high level languages
17:38:15
##forth
<cleobuline>
forthBot: MICRO WORDS MICRO SWAP - .
17:38:15
##forth
<forthBot>
USERNAME .S . + - * / MOD DUP DROP SWAP OVER ROT >R R> R@ = < > AND OR NOT XOR & | ^ ~ << >> CR EMIT VARIABLE @ ! +! DO LOOP I WORDS LOAD CREATE ALLOT ." CLOCK BEGIN WHILE REPEAT AGAIN SQRT UNLOOP +LOOP PICK CLEAR-STACK PRINT NUM-TO-BIN PRIME? FORGET STRING " 2DROP IMAGE TEMP-IMAGE CLEAR-STRINGS DELAY EXIT MICRO MILLI
17:38:15
##forth
<forthBot>
519
20:13:11
##forth
<vms14_>
I do not know how I'm going to store literals like strings or objects in a portable way
20:14:57
##forth
<vms14_>
I guess I can just target js and not worry about hardcoding stuff
20:15:02
##forth
<vms14_>
I could use json also
20:24:52
##forth
<crc>
I generally try to operate as if it were closer to a hardware computer; so things like strings get stored in the simulated RAM, and I implement functions using the instruction set to work with them
20:25:35
##forth
<crc>
in parable, I stored type information, and used JSON to store a representation of the memory and stacks
21:43:31
##forth
<vms14_>
yeah but it's weird to emulate memory just to add more overhead having to convert strings from an array sequence to a js string
21:44:01
##forth
<vms14_>
but then I compromise portability because I assume a gc
21:44:24
##forth
<vms14_>
I will just focus on js and that's it
21:44:55
##forth
<vms14_>
so the bytecode generator might spit some js code or alike, at the end what I want is an introduction to compiling/transpiling
21:46:08
##forth
<vms14_>
a bytecode interpreter looks like a good option for that
22:14:09
##forth
<xentrac>
implementing a GC if you don't have one isn't that hard
22:49:32
##forth
<cleobuline>
forthBot: LOAD "test.fth"
22:49:32
##forth
<forthBot>
Error: Error: LOAD: Cannot open file 'test.fth'
22:49:59
##forth
<cleobuline>
forthBot: LOAD "test.fth"
22:49:59
##forth
<forthBot>
Error: Error: LOAD: Cannot open file 'test.fth'
22:51:29
##forth
<cleobuline>
forth: LOAD "test.fth"
22:51:39
##forth
<cleobuline>
forth: LOAD "test2.fth"
22:51:47
##forth
<cleobuline>
forthBot: LOAD "test.fth"
22:51:56
##forth
<cleobuline>
forthBot: LOAD "test2.fth"
22:51:56
##forth
<forthBot>
Unknown word in definition: DAYS-IN-MONTH
22:51:56
##forth
<forthBot>
Error: Definition discarded due to error
22:56:39
##forth
<cleobuline>
forthBot: LOAD "test.fth"
22:56:50
##forth
<cleobuline>
forthBot: LOAD "test2.fth"
22:56:51
##forth
<forthBot>
Unknown word in definition: DAYS-IN-MONTH
22:56:51
##forth
<forthBot>
Error: Definition discarded due to error
22:57:16
##forth
<cleobuline>
forthBot: LOAD "test2.fth"
22:57:37
##forth
<cleobuline>
forthBot: TODAY-CAL-IRC
22:57:37
##forth
<forthBot>
May 2025
22:57:37
##forth
<forthBot>
Mo Tu We Th Fr Sa Su
22:57:38
##forth
<forthBot>
1 2 3 4
22:57:38
##forth
<forthBot>
5 6 7 8 9 10 11
22:57:39
##forth
<forthBot>
12 13 14 15 16 17 18
22:57:39
##forth
<forthBot>
19 20 21 22 23 24 25
22:57:39
##forth
<forthBot>
26 27 28 29 30 31
22:57:46
##forth
<cleobuline>
bug fixed
22:59:41
##forth
<MrMobius>
vms14: if you're emulating a block of memory with JS, make sure you know what "holey" and packed arrays are
23:01:49
##forth
<thrig>
bless with holy water? good against undead