I've been attempting to get an objective-c framework to work with macruby and I
believe I've found a bug in the way ruby Proc objects are copied when used as
objective-c blocks.
The copied block doesn't seem to persist correctly beyond the scope in which it
was copied. It isn't deallocated, but
Wait
You mean, Programming isn't a Religion? Seems to me, I'm always sacrificing
to the Coding Goddess for working code, no matter the language. lol
Just to lighten the mood, and in agreement, Hack and Slash those bits!
Mario
On Thu, Nov 18, 2010 at 11:52 AM, Eloy Duran wrote:
> You’re ri
Hi Alan,
I didn't look in further details yet, but clearly your initWithBlock method is
wrong, it should be:
- (id)initWithBlock:(void (^)())aBlock;
{
if ((self = [super init])) {
block = [aBlock copy];
NSLog(@"Block: %@", block);
block();
Whoops, sorry about that. I find that I can get away without assigning to self
in 'init' when doing a quick hack, but certainly not the recommended approach,
especially when attempting to track down another bug.
I've amended the initializer now and I still encounter the same problem.
Al
On 19 N
I see.
It would be ideal if you could provide a small test sample, so that we can
reproduce the bug :-)
--
Thibault Martin-Lagardette
On Nov 19, 2010, at 12:25, Alan Skipp wrote:
> Whoops, sorry about that. I find that I can get away without assigning to
> self in 'init' when doing a quick
Hi guys,
Gmail Notifr was originally written in RubyCocoa, which runs as a little
NSStatusBar app and checks your gmail feeds at specified intervals. I
started updating it to MacRuby last month.
Most changes were just simply updating method_arg1_arg2 to
method(arg1:arg2). Since this app saves acc
Thanks for sharing :)
On 19 Nov 2010, at 14:36, James Chen wrote:
> Hi guys,
>
> Gmail Notifr was originally written in RubyCocoa, which runs as a little
> NSStatusBar app and checks your gmail feeds at specified intervals. I started
> updating it to MacRuby last month.
>
> Most changes were
Hey James,
The C API for the Keychain is not annotated with a bridge support file by
default in SnowLeopard, so the first thing you'll need to do is install the
BridgeSupport preview. Then you need to know what to put in for the 4
parameters to the method call, which unfortunately is not documente
I don't think you need the BS preview for that. I can create a BS file with: $
gen_bridge_metadata -f Security -o Security.bridgesupport
On 19 nov 2010, at 20:39, Joshua Ballanco wrote:
> Hey James,
>
> The C API for the Keychain is not annotated with a bridge support file by
> default in Snow
Hi, thanks for the reply!!!
I1m using
MacOS1.6.3 &
MacRuby 1.7.1
And yes I have install Bridge Support preview. The funny thing is thet with
tha same version, system, etc the code is working on my iMac. but still does
not on my macbook.
Abny idea or suggestions? how to fix.
On Tue, Nov 16, 2010 a
Just to be sure, did you receive Thibault's response?
http://lists.macosforge.org/pipermail/macruby-devel/2010-November/006424.html
On 19 nov 2010, at 21:48, András Zalavári wrote:
> Hi, thanks for the reply!!!
> I1m using
> MacOS1.6.3 &
> MacRuby 1.7.1
> And yes I have install Bridge Support p
Thank you for your help, Josh.
The project used to use a generated Security.bridgesupport, then I decided
to build it on the nightly build (0.8) with BS Preview. I found ^v parameter
is supported in 0.8 (but not in 0.7). The API we discussed require several
more complicated pointer parameters I ha
Eloy,
Yes both works. Currently it depends on MacRuby 0.8 and BS preview (when
the app is ready for use if MacRuby is still not shipped with OSX, I believe
it could require both MacRuby and BridgeSupport).
Sent from my iPhone
On 2010/11/20, at 5:26, Eloy Duran wrote:
I don't think you need th
13 matches
Mail list logo
