2025-12-06 02:01:14 <MrMobius    > tpbsd: does nixos have the same packages as Ubuntu?
2025-12-06 02:06:33 <tpbsd       > MrMobius, pretty much, it has a enormous selection, but sxeems a bit thin with embedded
2025-12-06 02:07:33 <tpbsd       > MrMobius, it seems to have the MSP430 stuff
2025-12-06 02:08:15 <tpbsd       > MrMobius, it has the stlink stuff
2025-12-06 02:09:32 <tpbsd       > MrMobius, ahh here it is "gcc-arm-embedded-13"
2025-12-06 02:09:39 <tpbsd       > that has all the eabi stuff
2025-12-06 02:14:12 <MrMobius    > ya confusingly the various GCCs have a different name once installed than the package
2025-12-06 02:14:52 <tpbsd       > hmm, it doesnt seem to have everything
2025-12-06 02:15:15 <MrMobius    > I'm guessing that's the old 4.6 GCC for msp430 not the newer and incompatible 9.3 that TI commissioned
2025-12-06 02:15:21 <tpbsd       > I'll still install freebsd-15 on my spare pc, see how that goes
2025-12-06 02:16:57 <tpbsd       > dont know, it doesnt say
2025-12-06 02:19:23 <MrMobius    > One day I'll figure out the 6 or so different ways they've given us to program them in C. It's very confusing
2025-12-06 02:22:45 <tpbsd       > it is
2025-12-06 02:23:45 <tpbsd       > they only have various GCC versions but also differennt libraries ranging from open to STMlibs etc
2025-12-06 02:24:10 <tpbsd       > I think the libs are the confusing part
2025-12-06 02:24:30 <tpbsd       > as they supply the headers and includes oplus the API docs etc
2025-12-06 02:24:50 <tpbsd       > I think that C is just not well suited for embedded dev
2025-12-06 02:25:11 <tpbsd       > it's great for PC apps however
2025-12-06 02:26:13 <tpbsd       > Forth is far better suited for embedded as long as you can easily access the peripheral configs, and thats what FURS provides
2025-12-06 02:27:17 <tpbsd       > sure C provides smaller and faster binaries than Forth, no question, but the dev cycle is a pain
2025-12-06 02:27:35 <tpbsd       > (embedded)
2025-12-06 03:59:43 <MrMobius    > It's more manageable if they give you one thing to download and then that's it. ST did this last I checked. MicroChip used to make it harder but are more like ST now I think
2025-12-06 04:00:14 <MrMobius    > Also without charging for your shitty IDE
2025-12-06 04:12:18 <tpbsd       > last I tried, microchip was all windows or java for Linux
2025-12-06 04:12:50 <tpbsd       > I couldnt even build a flashforth kernel and gave up after a couple of days
2025-12-06 04:14:26 <tpbsd       > Ive given up on microchip now, ST has by far the better product especially in the 'G ' series STM32 imho
2025-12-06 08:59:23 <smlckz      > i've not written so much forth before, please take a look: https://0x0.st/KvPZ.fth
2025-12-06 09:00:52 <smlckz      > is there an ans forth way of making that word q work at compile time as well?
2025-12-06 10:05:59 <veltas      > smlckz: make q IMMEDIATE and check STATE and then either do current behaviour or POSTPONE POSTPONE the words
2025-12-06 10:07:36 <veltas      > I'm not 100% sure what you need to know since a lot is going on here but maybe that will help point you in right direction
2025-12-06 10:10:11 <veltas      > You've also got COMPILE, and EXECUTE to work with, might need to FIND your defs and check whether they're immediate etc
2025-12-06 10:10:22 <veltas      > Since you're doing a lot of the parsing yourself
2025-12-06 13:41:57 <cleobuline  > !uptime
2025-12-06 13:41:58 <LispBot860  > 124h 42min 28s
2025-12-06 16:14:46 <smlckz      > veltas: i am thinking of allocating the string and store the pointer and length that will be loaded at runtime of the word being compiled that called q
2025-12-06 16:22:15 <[[smlckz]]  > so POSTPONE LITERAL is it?
2025-12-06 19:06:49 <[[smlckz]]  > So it turns out like this http://0x0.st/KvAu.fth
2025-12-06 19:07:55 <[[smlckz]]  > Any suggestions to make the code better, more idiomatic (I wonder if that's a thing in Forth at all)?