Re: GSoC status report

Another update:

I've been concentrating on the module system as well as the modules since
the last update.  In order to get more familiar with it, I wrote a module
(using FFI) for libmagic. It's a bit "unlispy", though, providing only raw
access to the C functions and macros. (Passing keywords instead of or'ing
flags would probably be more idiomatic.)

Regarding gnulib and modules: One issue is about linking against gnulib
both for the main CLISP binary as well as for modules (like bindings/glibc).
In https://sourceforge.net/p/clisp/bugs/634/ you mention that the increased
size is not an issue on linux but possibly on other targets. Do you know
which targets?

I fear that there's not really a much better solution, though. One could
try to isolate a set of gnulib modules that are "guaranteed" to be (including
all unused functions, thus completely) linked with the CLISP binary, so that
all CLISP modules don't need to link against these parts of gnulib. This
might be fragile to maintain and keep in synch, though.

I also remember a post on the gnulib list (I think from Bruno) on building
part of gnulib as a shared library, but cannot find atm. (I think it was
MinGW related, too)

I've been also looking at generating the FFI forms (def-call-out and
friends) automatically (using libclang in order to parse header files), but
this is a bit out of scope.

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel