00:42:47
##forth
<cleobuline>
forthBot: : LOAD ini.fth
00:42:48
##forth
<forthBot>
Unknown word in definition: ini.fth
00:42:48
##forth
<forthBot>
Error: Definition discarded due to error
00:42:57
##forth
<cleobuline>
forthBot: LOAD ini.fth
00:42:58
##forth
<forthBot>
File ini.fth with moon loaded
00:43:03
##forth
<cleobuline>
forthBot: MOON
00:43:03
##forth
<forthBot>
Phase de la lune pour Fri June 6 2025
00:43:04
##forth
<forthBot>
🌔 Gibbeuse croissante La lune grossit, revez grand ce soir !
00:43:04
##forth
<forthBot>
75% illuminée
00:43:19
##forth
<cleobuline>
vivement la pleine lune !
02:43:03
##forth
<forthBot>
Environment for cleobuline inactive, freeing...
10:23:27
##forth
<olle>
I wonder if you could make an online survey tool entirely in a Forth-like DSL, instead of using CRUD GUI or WYSIWYG interface.
10:24:05
##forth
<olle>
Might be some interesting pros and cons.
10:24:30
##forth
<olle>
Because they normally already support different types of skip logic, like "if they're a man, don't show this question, only if woman", etc.
10:25:02
##forth
<olle>
Translations might not be suitable in this format. Or localization.
11:23:12
##forth
<veltas>
In subject of small C compilers, there's also cproc/QBE which are a C front-end and generic optimising back-end, both of which are quite small
11:23:31
##forth
<veltas>
Which I think is a bit more pragmatic, but seem less mature than tinycc
11:23:50
##forth
<veltas>
I'm going to play with those a bit myself when I get some free time, I don't get a lot at the moment!
11:24:39
##forth
<cleobuline>
forthBot: : LOAD ini.fth
11:24:39
##forth
<forthBot>
Unknown word in definition: ini.fth
11:24:39
##forth
<forthBot>
Error: Definition discarded due to error
11:24:45
##forth
<cleobuline>
forthBot: LOAD ini.fth
11:24:46
##forth
<forthBot>
File ini.fth with moon loaded
11:24:53
##forth
<cleobuline>
forthBot: MOON
11:24:53
##forth
<forthBot>
Phase de la lune pour Fri June 6 2025
11:24:54
##forth
<forthBot>
🌔 Gibbeuse croissante La lune grossit, revez grand ce soir !
11:24:54
##forth
<forthBot>
78% illuminée
11:25:08
##forth
<tpbsd>
veltas, are called 'small' becayse they are small exe size, or made for small mcus, like PIC's ?
11:35:11
##forth
<veltas>
tpbsd: Small codebase, don't know if they'd fit on a small MCU
11:35:37
##forth
<tpbsd>
veltas aha
11:35:58
##forth
<veltas>
I think for an MCU pcc is probably the best choice if you wanted to run a C compiler on there, but Forth is a better choice for compiling on the MCU
11:37:10
##forth
<tpbsd>
I was only curious what you meant, I only run Mecrisp-Stellaris Forth thesedays on cortex-m and MSP430
12:08:58
##forth
<veltas>
Because for example GCC and clang/LLVM are massive, in codebase and install size
12:09:30
##forth
<veltas>
GCC is so big that my laptop struggles to even grep the source code HEAD
12:10:58
##forth
<veltas>
tpbsd: Have you heard of the DRY programming concept, AKA "Don't Repeat Yourself"?
12:11:29
##forth
<veltas>
I think it applies a bit to Forth as well, I find it's more necessary the larger a codebase gets, or really the larger a module gets
12:12:03
##forth
<tpbsd>
no not really, but Im not really a programmer, I'm a hardware guy
12:16:08
##forth
<cleobuline>
il y a de l'eau dans le gaz entre Trump et Musk
13:24:53
##forth
<forthBot>
Environment for cleobuline inactive, freeing...
13:35:26
##forth
* anthk_ it's fine with cparser
23:05:20
##forth
<cleobuline>
forthBot: LOAD ini.fth
23:05:20
##forth
<forthBot>
File ini.fth with moon loaded
23:05:25
##forth
<cleobuline>
forthBot: MOON
23:05:25
##forth
<forthBot>
Phase de la lune pour Fri June 6 2025
23:05:25
##forth
<forthBot>
🌔 Gibbeuse croissante La lune grossit, revez grand ce soir ! Illumination 80%