14:07:15
##forth
<vms14>
it seems that gforth ffi already had a way to avoid recompiling every time and I didn't know it
14:07:18
##forth
<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.
14:08:35
##forth
<vms14>
that's cool
14:09:18
##forth
<vms14>
at the end gforth has the coolest ffi I have ever seen
14:09:28
##forth
<vms14>
or the easiest to use at least
14:28:40
##forth
<vms14>
I'm trying it and it works fine
14:29:04
##forth
<vms14>
it does only compile once, then reuses it
14:35:56
##forth
<vms14>
you need libtool-bin in debian or libtool in other unix-like systems
15:11:16
##forth
<pgimeno>
I beg to differ, I love LuaJIT's FFI because you don't even have to compile anything
15:12:05
##forth
<pgimeno>
I don't think you can beat that in terms of ease of usage :)
15:12:08
##forth
<vms14>
oh I didn't see it
15:12:30
##forth
<pgimeno>
it has a built-in C declaration parser
21:29:24
##forth
<vms14>
I'm adding bindings to xlib :D
22:04:49
##forth
<veltas>
I have vague memories of Zarutian sans iPad, maybe a hallucination though
22:05:52
##forth
<veltas>
My biggest complaint about gforth is .... if it has essentially a C compiler as a dependency then what's the point
22:06:45
##forth
<veltas>
You know what else interfaces well with C? C.
22:33:43
##forth
<vms14>
c does not have colon words
22:34:19
##forth
<MrMobius>
does it require all of gcc or just the assembler from binutils?
22:34:28
##forth
<MrMobius>
and linke
22:34:29
##forth
<MrMobius>
r
22:34:32
##forth
<vms14>
but in my case it's cool sinc I can play with libraries I like while learning forth
22:34:52
##forth
<vms14>
and I can use forth for cool projects, for example a window manager :0
22:35:11
##forth
<vms14>
it requires libtool-bin in debian
22:35:39
##forth
<vms14>
and I'm not sure on what libtool requires
22:36:00
##forth
<vms14>
I see people praising pforth and saying they extended it a bit with c
22:37:20
##forth
<thrig>
extending forth with C or assembly may not differ much
22:58:19
##forth
<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
22:58:50
##forth
<xentrac>
LuaJIT's is more complete, though; GForth doesn't support struct arguments and return values
22:59:42
##forth
<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++