On 10 August 2011 16:09, Igor Stasenko wrote:
> On 10 August 2011 15:44, Henrik Johansen wrote:
>> A couple of issues I've had:
>>
>> 1) handleFailureIn: aContext nativeCode: aBlock does not recover after
>> enabling native code for first time (successfully), but rather goes on to
>> signa
On 10 August 2011 15:44, Henrik Johansen wrote:
> A couple of issues I've had:
>
> 1) handleFailureIn: aContext nativeCode: aBlock does not recover after
> enabling native code for first time (successfully), but rather goes on to
> signal last error. (ie there'sno ifTrue: branch for enableN
A couple of issues I've had:
1) handleFailureIn: aContext nativeCode: aBlock does not recover after
enabling native code for first time (successfully), but rather goes on to
signal last error. (ie there'sno ifTrue: branch for enableNativeCode)
2) Trying to use the interpreterproxy directly
@Windows users:
Since Windows VMs currently not available on Jenkins server, i
uploaded a prebuilt VM
to NativeBoost project hosting:
http://code.google.com/p/nativeboost/downloads/detail?name=nb-cog-win32.zip&can=2&q=
I tested if new code works on windows. And after fixing couple of
glitches, it
Hello,
Major news: NativeBoost now working on Macs!
The main problem with Mac OS platform was that it requires a stack
alignment discipline, while other platforms don't.
So, i had to extend the assembler to make sure that all external calls
will be made with properly aligned stack.
Also, i spent
