2025-03-22 02:00:00 <cleobuline  > LOAD "test.fth"
2025-03-22 02:00:24 <cleobuline  > ForthBot:  EURO
2025-03-22 02:00:25 <ForthBot    > Unknown word: EURO
2025-03-22 02:00:57 <cleobuline  > ForthBot:  WORDS
2025-03-22 02:00:57 <ForthBot    > DP
2025-03-22 03:03:57 <cleobuline  > ForthBot: CLOCK .
2025-03-22 03:03:57 <ForthBot    > 1742609037
2025-03-22 03:04:43 <cleobuline  > ForthBot:  LOAD "test.fth"
2025-03-22 03:05:12 <cleobuline  > ForthBot:  LOTO
2025-03-22 03:05:12 <ForthBot    > 32 15 11 25 30 1
2025-03-22 03:29:56 <cleobuline  > ForthBot:  : years CLOCK 31536000 / . ." years since Unix epoch" ;
2025-03-22 03:31:01 <cleobuline  > ForthBot:  years
2025-03-22 03:31:01 <ForthBot    > 55
2025-03-22 12:32:10 <cleobuline  > hello
2025-03-22 12:39:01 <X-Scale     > be welcome, cleobuline
2025-03-22 12:51:20 <cleobuline  > georges foreman is dead
2025-03-22 12:51:28 <cleobuline  > sight !
2025-03-22 13:04:37 <cleobuline  > hello-operator:  X-Scale : comment va tu ?
2025-03-22 14:12:17 <cleobuline  > ForthBot:  LOAD "test.fth"
2025-03-22 14:12:56 <cleobuline  > now accept multilines definition in uploaded file https://github.com/cleobuline/some-c-sources/blob/main/forth_gmp_irc_bot.c
2025-03-22 14:13:39 <cleobuline  > next should accept multilines definition in chatbot
2025-03-22 16:04:08 <cleobuli_   > no multilines should be a garbages systèm
2025-03-22 16:04:51 <cleobuli_   > firs of all i must transform the bot to be multiuser .. big job to adapt
2025-03-22 16:05:56 <cleobuli_   > may be each user may have his own dictionnary too :)
2025-03-22 23:12:03 <cleobuline  > hello
2025-03-22 23:12:16 <cleobuline  > ForthBot:  123456789123457 PRIME? .
2025-03-22 23:12:17 <ForthBot    > 1
2025-03-22 23:12:22 <cleobuline  > i win !
2025-03-22 23:13:23 <cleobuline  > nice it's fast enough
2025-03-22 23:16:54 <cleobuline  > ForthBot:  123456789123457 3 *  123456789123457 5 * PGCD .
2025-03-22 23:16:54 <ForthBot    > 123456789123457
2025-03-22 23:25:42 <MrMobius    > how do Forths usually handle alignment? im working on a Forth for SH4  and writing an unaligned 32-bit value turns into writing each byte separately
2025-03-22 23:26:40 <MrMobius    > @ and ! could round the pointer up if it's unaligned but then you need to copy the rounded pointer back to what generated it
2025-03-22 23:42:45 <cleobuline  > ForthBot:  : INIT-RANDOM CLOCK SEED ! ;
2025-03-22 23:43:01 <cleobuline  > ForthBot:  1 100 RAND .
2025-03-22 23:43:02 <ForthBot    > 7
2025-03-22 23:43:10 <cleobuline  > ForthBot:  1 100 RAND .
2025-03-22 23:43:10 <ForthBot    > 76
2025-03-22 23:43:27 <cleobuline  > nice
2025-03-22 23:44:36 <amby        > MrMobius: depends on the host machine, i assume
2025-03-22 23:44:47 <amby        > x86 handles unaligned accesses transparently for you
2025-03-22 23:45:05 <amby        > you just lose atomicity (which tbh in a forth you're probably not concerned about) and a bit of performance
2025-03-22 23:45:28 <amby        > whereas arm shits itself and cries
2025-03-22 23:45:33 <MrMobius    > im asking because unaligned accesses on this architecture cause an exception
2025-03-22 23:46:12 <amby        > checking for alignment in every ! and @ is gonna be a bit slow
2025-03-22 23:46:31 <amby        > so you could have those just fault if the address isn't aligned
2025-03-22 23:46:44 <amby        > and then have some separate words for accessing addresses that aren't aligned
2025-03-22 23:47:13 <amby        > as a general rule you shouldnt need misaligned accesses unless you're scraping up the last few bits of memory
2025-03-22 23:48:06 <MrMobius    > heh im not sure "just fault" is a good solution
2025-03-22 23:48:52 <MrMobius    > if you let the users use ! and c! and so on as they like, how do you avoid misaligned access?
2025-03-22 23:50:01 <MrMobius    > it comes down to a contract with the user where if they dont follow they rules they pay the price which could be an exception but id like to avoid that