cffi-devel May 2007

cffi-devel@common-lisp.net

17 participants
16 discussions

[cffi-devel] unicode
by Tamas K Papp 16 May '07

16 May '07

Hi, What is the suggested method to pass unicode strings (const char* pointing to an utf8 string) to C functions in CFFI? I am using CMUCL. Thanks, Tamas

2 1

[cffi-devel] getting CFFI function signature
by Tamas K Papp 14 May '07

14 May '07

Hi, I have CFFI bindings generated by SWIG, which look like (cffi:defcfun ("cairo_line_to" cairo_line_to) :void (cr :pointer) (x :double) (y :double)) I would like to generate wrapper functions that would take the first argument from a global variable and apply conversions for the rest. The problem is that there are many functions, and I want to automate this as much as possible. Is there any way to get the signature of a function defined with cffi:defcfun? In this case, I need something like (:void cr :pointer x :double y: double) (of course the syntax and the ordering can vary). With this, I could automate the generation of wrappers. Thanks, Tamas

3 2

[cffi-devel] How to get free quality visitors to your website
by Hit＠common-lisp.net 08 May '07

08 May '07

1 0

[cffi-devel] Can you afford to lose 300.000 potential customers per year!?
by instant＠common-lisp.net 05 May '07

05 May '07

1 0

[cffi-devel] Feed Blaster puts your ad right to the screens of millions in 15 Minutes !
by Feed＠common-lisp.net 03 May '07

03 May '07

1 0

[cffi-devel] cffi-sys::default-encoding returns nil on clisp/mingw
by Jack Unrue 01 May '07

01 May '07

Running CLISP on my system with the newtypes branch, I find that the CFFI-SYS::DEFAULT-ENCODING function is returning NIL. Some poking around reveals that CUSTOM:*FOREIGN-ENCODING* is set to #<ENCODING CHARSET:CP1252 :DOS> I looked at the symbol values for everything in the :charset package, and they all specify :UNIX instead of :DOS and so that's what CFFI-SYS::*ENCODINGS* and CFFI-SYS::*CLISP-ENCODINGS* get populated with. So I can see why DEFAULT-ENCODING is returning NIL. Before I head over to clisp-devel and ask about this, I just wanted to see whether this situation surprises anyone here, or if you think it might be a CLISP build configuration issue (which would be funny because I'm one of the MingW package maintainers), or ??? For instance, can anyone point me at a spot in the CLISP manual that states that *FOREIGN-ENCODING* will always correspond to the value of one of the symbols in the :charset package? This is on WinXP SP2, CLISP 2.41 (mingw special) with nothing related to encoding for command-line arguments. -- Jack Unrue

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel May 2007