Re: Hello-C mailing list?

I had a look at CFFI and it does not seem to even contain a fraction of
what UFFI provides. I thought Hello-C was supposed to be a form from
UFFI, rather than a completely new library written from scratch.

Juanjo

.

Relevant Pages

  • Re: Hello-C mailing list?
    ... I thought Hello-C was supposed to be a form from UFFI, rather than a completely new library written from scratch. ... Because of the close relationship between the two projects, we thought we would discuss them both on the Fetter list. ... Meanwhile the CFFI developer has responded positively to Hello-C extending his work, so the source will be in a branch of the CFFI CVS tree for now. ...
    (comp.lang.lisp)
  • Re: Hello-C mailing list?
    ... There is a mailing list related to Hello-C on this page. ... >I had a look at CFFI and it does not seem to even contain a fraction of ... >UFFI, rather than a completely new library written from scratch. ... Interface. ...
    (comp.lang.lisp)
  • Re: cl-sockets, Google, Lisp-NYC, and The Savages of c.l.l
    ... CFFI, or something similar? ... CLSQL looks rather poor so far in comparison to the ... Or do you think UFFI is either portable or efficient on all platforms? ... Apologies now if that is gross misinformation, but to me the only thing that matters is making all C/C++ libraries effectively also Lisp libraries. ...
    (comp.lang.lisp)
  • Re: New to Lisp: UFFI, CFFI, and osicat, oh my!
    ... > work with anything which requires either CFFI or UFFI. ... cffi-uffi-compat instead of uffi. ... It'd probably be easier to just convert osicat to use CFFI ...
    (comp.lang.lisp)
  • Re: Arity of a closure and a Lisp Community Process
    ... portability layers, ... CLSQL mailing lists and ask yourself why CFFI was invented when UFFI ... does CFFI cover /everything/ the LispWorks FFI (for ...
    (comp.lang.lisp)