Here's a thought: leverage the excellent work already done
for the swig clisp bindings: the output produced by swig
-clisp -c++ somefiletobind.i looks like it wouldn't be too
difficult to munge into gst code either with gst itself or
maybe with emacs elisp ....
Brad Watson
----- Original Message ----
From: Paolo Bonzini <paolo.bonzini lu.unisi.ch>
To: Krishna <v.krishnakrishna gmail.com>
Cc: help-smalltalk gnu.org
Sent: Monday, November 20, 2006 12:37:15 AM
Subject: Re: [Help-smalltalk] Re: freeglut and opengl
bindings
>> I have no idea of the complexity of this task. It
seems relatively
>> similar to JNI, which SWIG supports, in terms of
complexity...
>
> Oh!, I thought it is closer to the CLISP FFI (which
SWIG supports too).
Might be. As far as I could see, the biggest design choice
is whether
the C function gets the argument count and an argument
vector, or rather
the arguments already converted to C data types and placed
into
different arguments. Python for example is the former, Java
is the latter.
Paolo
_______________________________________________
help-smalltalk mailing list
help-smalltalk gnu.org
http://lists.gnu.org/mailman/listinfo/help-smalltalk
____________________________________________________________
________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
a>
_______________________________________________
help-smalltalk mailing list
help-smalltalk gnu.org
http://lists.gnu.org/mailman/listinfo/help-smalltalk
|