On 26 September 2010 06:43, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Sig,
Today, I ran into a bug of mine that I would not have had to track down if the various typed byte arrays (double in particular) existed. Â The more you can offer in that area, with indexing, bulk fill, bulk copy, etc., the better.
I also ran into what appears to be a maximum number of arguments to an external call. Â Can you get around that? Â I can too, in this case. Â It's shameless, but I will "dumb down" the call so that FFI can handle it. Â There are arguments that I can default or provide from a shared library, and just call into a facade function exported from there. Â Shouldn't have to do that, clearly, but it will work.
NB supports facade calls. And i'm using them a lot, since many functions having default values, which never change. There's one limitation, that constant arguments should be 32-bit int/uint. In function spec you can put integer constants or class/pool variables. Suppose you have a C function foo( int x , int y) so, FFI allows you to use only in this style: fooX: x y: y <primitive ... > ^ NBFFICallout cdecl: #( foo (int x, int y) ) module: 'bar' i.e. , method arguments 1:1 matching function argument. With NB, however you can pass them in arbitraty order, or push same argument twice, like: fooX: x <primitive ... > ^ NBFFICallout cdecl: #( foo (int x, byte x) ) module: 'bar' or use constants: fooX: x <primitive ... > ^ NBFFICallout cdecl: #( foo (int x, 0 ) ) module: 'bar' so, y argument will be zero. or use class/pool vars for constants: fooX: x <primitive ... > ^ NBFFICallout cdecl: #( foo (int x, SomeClassVar ) ) module: 'bar' so, it will use a SomeClassVar value at the moment of code generation. or use inst vars as arguments: Point>>foo <primitive ... > ^ NBFFICallout cdecl: #( foo (int x, int y) ) module: 'bar' it will use receiver's x and y instance variables to coerce&push them as arguments. You also can use self (receiver) as an argument name, but then, obviously you have to tell NB how to coerce instance of your class to some C type.
Bill
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.