Memory Allocation Problem about nodobjc HOT 5 CLOSED

Should have mentioned that in:

var abc = $.NSMakeRect(0, 0, 500, 500);
console.log(abc);
var abcd = $.NSMakeRect(0, 0, 600, 600);
console.log(abcd);

both return the same memory address.

Also, not sure if this is related, but trying to get an NSRect returned from a window also causes a segfault:

// Both the following lines segfault:
win('contentView')('frame');
win('frame');

Thanks,
Thomas

from nodobjc.

I've confirmed this as well, i'm unsure as to the issue but it seems to be a node-ffi vs ffi issue, the ffi package hasn't been updated in some time as a dependency, ffi package seems to have changed its api significantly making upgrading a bit harder.

from nodobjc.

@tjbaron This is an issue with the previous libffi (pre-1.0), however the new libffi(1.0+) doesn't have this issue. However the NodObjC master branch relies on libffi pre-1.0, you can use the 1.0-ffi branch on the repo to fix this issue.

@TooTallNate It might be worth considering merging the 1.0 ffi branch onto master and update the npm distro so its up to date with node-ffi > 1.0. Just a thought.

from nodobjc.

Fixed on https://github.com/TooTallNate/NodObjC/tree/0.1.0, waiting for test/docs/merge

from nodobjc.

Fixed and merged, there's a unit test for this now: https://github.com/TooTallNate/NodObjC/blob/master/test/struct-test.js

from nodobjc.