[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-13 Thread Guy Hylton
Igor, P.S. The configuration is freshly-baked, i didn't even checked if it loads cleanly or not.. so, i don't recommend updating it in image with your precious code :) I have tried loading your updated Configuration into Pharo1.4 #14438 and it loaded ok, but as a NativeBoost beginner it took

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-13 Thread Igor Stasenko
On 13 September 2012 09:18, Guy Hylton guygant...@gmail.com wrote: Igor, P.S. The configuration is freshly-baked, i didn't even checked if it loads cleanly or not.. so, i don't recommend updating it in image with your precious code :) I have tried loading your updated Configuration into

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-13 Thread Igor Stasenko
Oh, yeah.. and this sort of problems (with re-initialization). It would be nice to have them solved automatically. I think it was bad idea to cache fields in NBExternalStructure. It would be better to solve that differently. On 13 September 2012 09:18, Guy Hylton guygant...@gmail.com wrote:

[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-13 Thread Guy Hylton
just give me your squeaksource account, so i can add you as developer. grh Oh, yeah.. and this sort of problems (with re-initialization). It would be nice to have them solved automatically. I think it was bad idea to cache fields in NBExternalStructure. It would be better to solve that

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-13 Thread Igor Stasenko
On 13 September 2012 14:06, Guy Hylton guygant...@gmail.com wrote: just give me your squeaksource account, so i can add you as developer. grh done. Oh, yeah.. and this sort of problems (with re-initialization). It would be nice to have them solved automatically. I think it was bad idea to

[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-02 Thread Igor Stasenko
Hi, i was in a mood of making some overhauls.. so as result i refurbished a type system a bit.. removed all bogus C-like class names , e.g. NBUnsignedIntType ... and replaced them with nice and uniform names, like NBUInt32, NBInt16 etc. (thanks Marten Feldtmann for an idea) A uniform type

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-02 Thread Lawson English
On 9/2/12 6:32 PM, Igor Stasenko wrote: Hi, i was in a mood of making some overhauls.. so as result i refurbished a type system a bit.. removed all bogus C-like class names , e.g. NBUnsignedIntType ... [...] P.P.S. i would really like some help with testing what i did, including writing some

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-02 Thread Igor Stasenko
On 3 September 2012 04:34, Lawson English lengli...@cox.net wrote: On 9/2/12 6:32 PM, Igor Stasenko wrote: Hi, i was in a mood of making some overhauls.. so as result i refurbished a type system a bit.. removed all bogus C-like class names , e.g. NBUnsignedIntType ... [...] P.P.S. i

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

2012-09-02 Thread Marten Feldtmann
Hello Igor, I think, that unifom indexing is a must. The usage/handling of NBExternalAddress must be equal to instances of ByteArray: at least as long as we have synchronous callouts, where a garbage collector is not able to move the byte array around in Smalltalk memory during the callout.