IRC Log - 2025-09-01 - ##forth

Channel: ##forth
Total messages: 67
Time range: 02:55:26 - 16:58:55
Most active: vms14 (40), xentrac (14), veltas (8)
02:55:26 ##forth <vms14> why the heck c-value is documented in gforth's ffi but does not fucking exist?
02:55:38 ##forth <vms14> Undefined word >>>c-value<<<
02:55:55 ##forth <vms14> yet here is documented https://gforth.org/manual/Declaring-C-Functions.html
03:01:10 ##forth <vms14> maybe i have an old version
03:02:57 ##forth <vms14> seems to be the reason
03:03:00 ##forth <vms14> gforth 0.7.3
03:12:21 ##forth <vms14> :0 newest gforth comes with xlib bindings
04:43:10 ##forth <vms14> it installed the entire world, but there are no xlib bindings
04:43:41 ##forth <vms14> yet it comes with minos2 and there is a file x11-actors that says "also x11" yet there is no x11 nowhere :/
05:03:01 ##forth <vms14> oh i have found the x.fs file :D
05:03:57 ##forth <vms14> i just had to include unix/x.fs
05:58:34 ##forth <vms14> https://termbin.com/jwyb
05:58:41 ##forth <vms14> this is cool
13:58:34 ##forth <veltas> I think the point of programming language standards is to produce code that scares people trained on the last revision of the standard where it was broken
14:08:21 ##forth <xentrac> vms14: yay xlib bindings!
14:08:31 ##forth <xentrac> I didn't know about include unix/x.fs
14:09:08 ##forth <vms14> xentrac: you have to update gforth
14:09:29 ##forth <xentrac> yeah, I also have 0.7.3 which doesn't have it
14:09:33 ##forth <vms14> https://gforth.org/
14:09:48 ##forth <vms14> download the bleeding edge version
14:09:54 ##forth <vms14> then run the commands there
14:09:55 ##forth <xentrac> veltas: what do you mean?
14:10:05 ##forth <vms14> it will install the entire universe though
14:10:16 ##forth <vms14> but it comes with xlib bindings, opengl, etc
14:10:36 ##forth <xentrac> I should add GForth bindings to Yeso
14:10:53 ##forth <veltas> xentrac: e.g. C++ code that uses globals makes me cringe because I 'know' that's bad, but since constexpr constructors have been added it's more safe now for some things
14:11:50 ##forth <xentrac> because of the static initialization order fiasco?
14:11:55 ##forth <veltas> Yeah
14:12:10 ##forth <xentrac> interesting, I didn't realize constexpr was relevant to that
14:12:37 ##forth <xentrac> the nice thing about C++ is that there's always so much more to learn?
14:12:49 ##forth <veltas> Well if it's constexpr doesn't that mean it's safe wrt order of init?
14:13:05 ##forth <veltas> Wow deja vu, feel like I've had this conversation before
14:14:37 ##forth <xentrac> I'm sure you're right
14:24:08 ##forth <vms14> btw the code i shown is terribly wrong xD
14:24:23 ##forth <vms14> i forgot to actually execute the open-display word
14:24:41 ##forth <vms14> it works because i have put a [ ] inside it xD
14:25:13 ##forth <vms14> but i actually just wanted to add the if, so that [] should be outside and the word just check
14:28:17 ##forth <vms14> also i see that it takes a s" string instead of s\" " drop i'm not sure if the stable version supports that, but c-function accepts s as argument which will take a s" string
14:29:29 ##forth <vms14> i was using s\" ...\0" to add the null for c because i did not know i could actually put s instead of a in the stack notation for c-function
14:29:46 ##forth <vms14> although not sure if that is available in the stable version
14:33:11 ##forth <vms14> it's not documented https://gforth.org/manual/Declaring-C-Functions.html
14:33:32 ##forth <vms14> but i have seen it in the unix/x.fs file
14:34:07 ##forth <vms14> that's the file
14:34:10 ##forth <vms14> https://termbin.com/4zz6
14:36:04 ##forth <vms14> also i do not know how is he adding the I flag for the compiler
14:37:04 ##forth <vms14> i see s" X11 -lXext" add-lib
14:39:11 ##forth <vms14> and seems that gforth structures map to c structures
14:39:50 ##forth <vms14> i don't know if it's new, because i thought i had to create my own c functions to mess with them
14:49:19 ##forth <xentrac> that's awesome!
14:49:42 ##forth <xentrac> I imagine it's a thing that hasn't changed and which might be platform-dependent
14:50:14 ##forth <xentrac> I mean you could imagine that on some platform the padding between struct members might differ between GForth and C
14:50:24 ##forth <xentrac> but that's not so likely to change over time
14:51:57 ##forth <vms14> btw now gforth uses swig to generate the .fs files for ffi
14:52:32 ##forth <vms14> idk if you are going to update it, but swig should help you automate bindings if you want to create them
14:52:53 ##forth <vms14> although i know nothing about swig xd
14:54:04 ##forth <cleobuline> forthBot: S" Donald Trump en etat de grace dans les nuages , en compagnie d'anges "S IMAGE
14:54:05 ##forth <vms14> would be cool to be able to ask mr paysan random questions
14:54:07 ##forth <forthBot> DEBUG: No 'url' key found in OpenAI response
14:54:07 ##forth <forthBot> Error: IMAGE: Failed to generate or upload image
14:54:29 ##forth <vms14> cleobuline: some users left the channel because you wouldn't stop spamming with your bot
14:54:48 ##forth <cleobuline> forthBot: EXIT
14:58:13 ##forth <xentrac> it's amazing that SWIG is still a thing
16:49:39 ##forth <cleobuline> vms14: anyone can type "forthBot: EXIT
16:50:12 ##forth <vms14> no one will though
16:54:50 ##forth <veltas> It's Kermit day
16:58:55 ##forth <veltas> "reminding you to make a little time for yourself"