Thanks for opening a ticket and describing the issue so well!
I'm not sure how this should be solved, but I was wondering how things
currently work for other C structs like NSRect or NSPoint. Are these handled as
special cases, or is there a more general way to deal with C structs?
Would it ma
nd instance methods and return true for those you
> support.
>
> On 15 nov 2010, at 00:15, Martijn Walraven wrote:
>
>> Hi,
>>
>> I was wondering if there is any way to formally indicate a MacRuby class
>> conforms to an Objective-C protocol. I encountered some co
Hi,
I was wondering if there is any way to formally indicate a MacRuby class
conforms to an Objective-C protocol. I encountered some code that uses
conformsToProtocol: instead of respondsToSelector: as a check before invoking
delegate methods, and the only way I could get a delegate written in
ou please
> check if there is already an open ticket, if not, please open one.
>
> Thx
>
> - Matt
>
> Sent from my iPhone
>
> On Nov 14, 2010, at 3:05, Martijn Walraven
> wrote:
>
>> Hi,
>>
>> I've looked into the issue some more, an
Hi,
I've looked into the issue some more, and it turns out the backtraces created
by MacRuby nightly are much more similar to the 1.9.2 ones. The backtrace still
misses the line referring to the actual execution of the spec though, so the
problem hasn't been completely solved yet.
It seems thi
Hi,
I'm trying to use RSpec (latest version, 2.1.0) with MacRuby, but there seems
to be information missing from the exception backtraces which makes it
difficult to see where exactly specs fail.
Running a straightforward helloworld_spec.rb with a failing example for
instance, shows a referenc
