2025-01-26 14:07:15 <vms14       > it seems that gforth ffi already had a way to avoid recompiling every time and I didn't know it
2025-01-26 14:07:18 <vms14       > The effect of giving such a name to the interface is that the generated files will contain that name, and when you use the interface a second time, it will use the existing files instead of generating and compiling them again, saving you time.
2025-01-26 14:07:27 <vms14       > https://www.complang.tuwien.ac.at/forth/gforth/Docs-html/Defining-library-interfaces.html#Defining-library-interfaces
2025-01-26 14:08:35 <vms14       > that's cool
2025-01-26 14:09:18 <vms14       > at the end gforth has the coolest ffi I have ever seen
2025-01-26 14:09:28 <vms14       > or the easiest to use at least
2025-01-26 14:28:40 <vms14       > I'm trying it and it works fine
2025-01-26 14:29:04 <vms14       > it does only compile once, then reuses it
2025-01-26 14:35:25 <vms14       > https://termbin.com/zhef
2025-01-26 14:35:56 <vms14       > you need libtool-bin in debian or libtool in other unix-like systems
2025-01-26 15:11:16 <pgimeno     > I beg to differ, I love LuaJIT's FFI because you don't even have to compile anything
2025-01-26 15:12:05 <pgimeno     > I don't think you can beat that in terms of ease of usage :)
2025-01-26 15:12:08 <vms14       > oh I didn't see it
2025-01-26 15:12:30 <pgimeno     > it has a built-in C declaration parser
2025-01-26 15:12:32 <vms14       > https://luajit.org/ext_ffi.html
2025-01-26 21:29:16 <vms14       > https://termbin.com/45qx
2025-01-26 21:29:24 <vms14       > I'm adding bindings to xlib :D
2025-01-26 22:04:49 <veltas      > I have vague memories of Zarutian sans iPad, maybe a hallucination though
2025-01-26 22:05:52 <veltas      > My biggest complaint about gforth is .... if it has essentially a C compiler as a dependency then what's the point
2025-01-26 22:06:45 <veltas      > You know what else interfaces well with C?  C.
2025-01-26 22:33:43 <vms14       > c does not have colon words
2025-01-26 22:34:19 <MrMobius    > does it require all of gcc or just the assembler from binutils?
2025-01-26 22:34:28 <MrMobius    > and linke
2025-01-26 22:34:29 <MrMobius    > r
2025-01-26 22:34:32 <vms14       > but in my case it's cool sinc I can play with libraries I like while learning forth
2025-01-26 22:34:52 <vms14       > and I can use forth for cool projects, for example a window manager :0
2025-01-26 22:35:11 <vms14       > it requires libtool-bin in debian
2025-01-26 22:35:39 <vms14       > and I'm not sure on what libtool requires
2025-01-26 22:36:00 <vms14       > I see people praising pforth and saying they extended it a bit with c
2025-01-26 22:37:20 <thrig       > extending forth with C or assembly may not differ much
2025-01-26 22:58:19 <xentrac     > LuaJIT's FFI is about equivalent to GForth's in terms of ease of use, but LuaJIT uses its own built-in C compiler, while GForth calls out to an external one
2025-01-26 22:58:50 <xentrac     > LuaJIT's is more complete, though; GForth doesn't support struct arguments and return values
2025-01-26 22:59:42 <xentrac     > MrMobius: GForth's FFI requires the C-compiler part of GCC, but not all of GCC.  For example, it doesn't care about GCC's support for Ada, D, or even C++