August 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [NB] Passing a null value to a const char* parameter

by StÃ©phane Ducasse

On Aug 24, 2012, at 5:49 PM, Igor Stasenko wrote: > On 24 August 2012 17:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Igor >> >> we should collect all the emails of Jan and turn them into a section in the FFI chapter. >> > sure. > meanwhile i will write a section about strings and structures on NB-Help. excellent idea. This evening I will read it if I do not fall asleep before since I should read mariano's paper ;D Stef > >> Stef >> >> On Aug 24, 2012, at 5:36 PM, Igor Stasenko wrote: >> >>> On 24 August 2012 17:00, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: >>>> Hello, >>>> >>>> NativeBoost doesn't allow me to pass a nil value instead of a String as a >>>> parameter for a 'const char*' function argument. When I use nil I get a >>>> failure with lastError=1 >>>> >>>> Is this by design? If so, is there an alternative? >>>> >>> yess.. >>> >>> by default if you use in signature a 'String' as argument type >>> then the FFI routine will only accept an instances of variable-byte >>> objects (which a ByteStrings are). >>> But there is an option #optStringOrNull >>> which will also allows passing a nil object as argument (which will be >>> converted to NULL pointer value) >>> >>> so, in your binding you must specify this option: >>> >>> mymethod: string >>> <...> >>> ^ self nbCall: #( void whatever(String string)) options: #( optStringOrNull ) >>> >>> so, for passing null , you can simply pass a nil as argument: >>> >>> self mymethod: nil. >>> >>>> Jan. >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > > > > -- > Best regards, > Igor Stasenko. >

Aug. 24, 2012

Re: [Pharo-project] RGMethodDefininition

by Camillo Bruni

I think instead of having a 'package' instVar we should have something like 'origin'. I remember adding #origin to CompiledMethod simplifying quite a bit. On 2012-08-24, at 17:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Good point > I'm not sure that we handled that. > > On Aug 24, 2012, at 4:56 PM, Camillo Bruni wrote: > >> How can I figure out whether an RGMethodDefininition is coming from a Trait? >> >> method := (DatePrintFormatTester >> #shouldFix:). >> method origin isTrait "returns true". >> >> how can I do the same with Ring?

Aug. 24, 2012

Re: [Pharo-project] [NB] Passing a null value to a const char* parameter

by Igor Stasenko

On 24 August 2012 17:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor > > we should collect all the emails of Jan and turn them into a section in the FFI chapter. > sure. meanwhile i will write a section about strings and structures on NB-Help. > Stef > > On Aug 24, 2012, at 5:36 PM, Igor Stasenko wrote: > >> On 24 August 2012 17:00, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: >>> Hello, >>> >>> NativeBoost doesn't allow me to pass a nil value instead of a String as a >>> parameter for a 'const char*' function argument. When I use nil I get a >>> failure with lastError=1 >>> >>> Is this by design? If so, is there an alternative? >>> >> yess.. >> >> by default if you use in signature a 'String' as argument type >> then the FFI routine will only accept an instances of variable-byte >> objects (which a ByteStrings are). >> But there is an option #optStringOrNull >> which will also allows passing a nil object as argument (which will be >> converted to NULL pointer value) >> >> so, in your binding you must specify this option: >> >> mymethod: string >> <...> >> ^ self nbCall: #( void whatever(String string)) options: #( optStringOrNull ) >> >> so, for passing null , you can simply pass a nil as argument: >> >> self mymethod: nil. >> >>> Jan. >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Aug. 24, 2012

Re: [Pharo-project] [NB] Problem with releasing a NBExternalObject

by StÃ©phane Ducasse

Thanks! I'm sorry to be a bit out since a couple of months but I'm trying to get back on shape. Stef >> this can be solved by adding an extra pharo-14-compat package and >> writing a configuration >> in a way that it will load that package in 1.4 but not in 2.0.. >> but this is tedious, and frankly i didn't learned well, how to do that >> trick with metacello. > > Next week we are going to build such a package (that adds methods to 1.3 or 1.4 so that lib writers can better follow new 2.0 api, I need it for Zn too). > > Sven

Aug. 24, 2012

Re: [Pharo-project] RGMethodDefininition

by StÃ©phane Ducasse

Good point I'm not sure that we handled that. On Aug 24, 2012, at 4:56 PM, Camillo Bruni wrote: > How can I figure out whether an RGMethodDefininition is coming from a Trait? > > method := (DatePrintFormatTester >> #shouldFix:). > method origin isTrait "returns true". > > how can I do the same with Ring? >

Aug. 24, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.3

by StÃ©phane Ducasse

thanks a lot for this new version. On Aug 24, 2012, at 3:24 PM, Igor Stasenko wrote: > Hi, all > > yesteray i committed new version of NativeBoost configuration. > > Some details about last few months changes: > > NativeBoost: > > - introduced a NBExternalTypeValue class > - introduced a NBNativeFunction class, a reification of external > function generated dynamically > - introduced an NBExternalResourceManager and integration with other classes > - a lot of cleanup and better comments > - some updates to NativeBoost-Help package (currently it is not part > of configuration by default, so you have to > load this package manually from NB repository) > > AsmJit: > > - the package is split on several small packages + configuration to load it > - more documentation > - more nicer instruction printing output > - fixed some instructions (some FPU / jump instructions was non-functional) > - and a lot of effort by Camillo, who made x64 assembler working. (but > we cannot use it with NB since our VMs is 32bit) > > To load NativeBoost you can follow an instructions on project page: > > > -- > Best regards, > Igor Stasenko. >

Aug. 24, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.3

by StÃ©phane Ducasse

;D Stef On Aug 24, 2012, at 3:49 PM, Igor Stasenko wrote: >> To load NativeBoost you can follow an instructions on project page: >> > http://code.google.com/p/nativeboost/wiki/Installation > > > -- > Best regards, > Igor Stasenko. >

Aug. 24, 2012

Re: [Pharo-project] [NB] Passing a null value to a const char* parameter

by StÃ©phane Ducasse

Igor we should collect all the emails of Jan and turn them into a section in the FFI chapter. Stef On Aug 24, 2012, at 5:36 PM, Igor Stasenko wrote: > On 24 August 2012 17:00, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: >> Hello, >> >> NativeBoost doesn't allow me to pass a nil value instead of a String as a >> parameter for a 'const char*' function argument. When I use nil I get a >> failure with lastError=1 >> >> Is this by design? If so, is there an alternative? >> > yess.. > > by default if you use in signature a 'String' as argument type > then the FFI routine will only accept an instances of variable-byte > objects (which a ByteStrings are). > But there is an option #optStringOrNull > which will also allows passing a nil object as argument (which will be > converted to NULL pointer value) > > so, in your binding you must specify this option: > > mymethod: string > <...> > ^ self nbCall: #( void whatever(String string)) options: #( optStringOrNull ) > > so, for passing null , you can simply pass a nil as argument: > > self mymethod: nil. > >> Jan. > > > > -- > Best regards, > Igor Stasenko. >

Aug. 24, 2012

Re: [Pharo-project] [NB] Problem with releasing a NBExternalObject

by Igor Stasenko

ok, i uploaded the fix. it is in v 1.3. so if you reload this version of ConfigurationOfNativeBoost, it should install the fixed latest versions of packages. -- Best regards, Igor Stasenko.

Aug. 24, 2012

Re: [Pharo-project] [NB] Passing a null value to a const char* parameter

by Igor Stasenko

On 24 August 2012 17:00, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: > Hello, > > NativeBoost doesn't allow me to pass a nil value instead of a String as a > parameter for a 'const char*' function argument. When I use nil I get a > failure with lastError=1 > > Is this by design? If so, is there an alternative? > yess.. by default if you use in signature a 'String' as argument type then the FFI routine will only accept an instances of variable-byte objects (which a ByteStrings are). But there is an option #optStringOrNull which will also allows passing a nil object as argument (which will be converted to NULL pointer value) so, in your binding you must specify this option: mymethod: string <...> ^ self nbCall: #( void whatever(String string)) options: #( optStringOrNull ) so, for passing null , you can simply pass a nil as argument: self mymethod: nil. > Jan. -- Best regards, Igor Stasenko.

Aug. 24, 2012