Hi all,
there seems to be a minor incompatibility between the latest UFFI and CFFI-UFFI-COMPAT: the LOOKUP-FOREIGN-ENCODING function is missing in the compat package.
It is easy to fix by copy-pasting this function implementation from the UFFI i18n.lisp sources (see the attached patch).
Could you please include it into the next CFFI release?
Thanks, Victor
On Wed, Oct 9, 2013 at 1:36 PM, Victor bobbie@ua.fm wrote:
there seems to be a minor incompatibility between the latest UFFI and CFFI-UFFI-COMPAT: the LOOKUP-FOREIGN-ENCODING function is missing in the compat package.
What is this function supposed to do? Is its return value supposed to be passed to other UFFI functions or CL functions?
On Wed, 09 Oct 2013 17:42:53 +0300, Luís Oliveira loliveira@common-lisp.net wrote:
On Wed, Oct 9, 2013 at 1:36 PM, Victor bobbie@ua.fm wrote:
there seems to be a minor incompatibility between the latest UFFI and CFFI-UFFI-COMPAT: the LOOKUP-FOREIGN-ENCODING function is missing in the compat package.
What is this function supposed to do? Is its return value supposed to be passed to other UFFI functions or CL functions?
Due to limited knowledge of UFFI and CFFI it is difficult to tell. But as far as I understand this function translates UFFI names for foreign encodings into platform-dependent names.
It is used multiple times in UFFI sources i18n.lisp and strings.lisp
Thanks, Victor
On Wed, Oct 9, 2013 at 3:57 PM, Victor bobbie@ua.fm wrote:
Due to limited knowledge of UFFI and CFFI it is difficult to tell. But as far as I understand this function translates UFFI names for foreign encodings into platform-dependent names.
Well, you probably found this by trying to run some code that uses UFFI. What is that code doing with LOOKUP-FOREIGN-ENCODING?
-
Luís Oliveira -
Victor