Re: GSoC 2016: proposal accepted!
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <4779FE7B0FF61A4998104E492AD7D6BC014480C008F1@HE110882.EMEA1.CDS.T-INTERNAL.COM> |
Daniel Jour wrote: >Do you know whether there are "workarounds" around libffcall bugs in CLISP's code? There shouldn't be. At the start, CLISP and ffcall were in the same hands: Bruno Haible. One day, Bruno realized that other projects could make use (or already had?) of the ffcall stuff and separated it as a library that he maintained for several years. At some time, the ffcall source moved out of the clisp source tree. When the packages are maintained, all is well. When not, your situation is not unlike Debian, Suse, Ubuntu etc. maintainers' job: have some patches (to libffcall, not clisp) at hand to keep them running... It's best if the patches are on the bug tracker of the ffcall project. This would p.o. lots of people, but you could consider building clisp without FFI, that's quite a task already. Please discuss priorities with your mentor. Regards, Jörg Höhle ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel