sound really as some bug.. and similar to system() call.
my versions is:
- it could be that strings are expected to be 16-byte aligned
- that there's some bug with converting to null-terminated C string

Great! It's be nice to get this and system calls working in one shot... how do we proceed? How do we test? I'm willing to help...

Cheers,
Sean

View this message in context: Re: NativeBoost String Handling Bug?
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.