Re: [MacRuby-devel] [MacRuby] #198: Bug in class constant lookup.

2009-01-06 Thread MacRuby
#198: Bug in class constant lookup. -+-- Reporter: eloy.de.en...@… |Owner: lsansone...@… Type: defect | Status: closed Priority: blocker

Re: [MacRuby-devel] [MacRuby] #182: The constant lookup in MacRuby does not behave correctly

2009-01-06 Thread MacRuby
#182: The constant lookup in MacRuby does not behave correctly +--- Reporter: vincent.isamb...@… | Owner: lsansone...@… Type: defect | Status: new Pr

Re: [MacRuby-devel] [MacRuby] #198: Bug in class constant lookup.

2009-01-06 Thread MacRuby
#198: Bug in class constant lookup. -+-- Reporter: eloy.de.en...@… | Owner: lsansone...@… Type: defect | Status: new Priority: blocker

[MacRuby-devel] Introduction

2009-01-06 Thread Giampiero De Ciantis
Hi everyone, I am new to the mailing list. Looking forward to watching MacRuby evolve. Would love to help somehow. -Gp ___ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [MacRuby] #199: Calling super from #respond_to? causes SystemStackError

2009-01-06 Thread MacRuby
#199: Calling super from #respond_to? causes SystemStackError -+-- Reporter: eloy.de.en...@… | Owner: lsansone...@… Type: defect | Status: new Priority:

[MacRuby-devel] [MacRuby] #198: Bug in class constant lookup.

2009-01-06 Thread MacRuby
#198: Bug in class constant lookup. -+-- Reporter: eloy.de.en...@… | Owner: lsansone...@… Type: defect | Status: new Priority: blocker

Re: [MacRuby-devel] Warnings about removing methods

2009-01-06 Thread Eloy Duran
Yes, that might be a better option. In my naivety, I mentioned this to Laurent as well, but it got lost in the discussion a bit. So Laurent, any input? Eloy On Jan 6, 2009, at 11:17 AM, Matt Mower wrote: On Tue, Jan 6, 2009 at 9:55 AM, Eloy Duran wrote: on pure objc classes. It would rem

Re: [MacRuby-devel] Warnings about removing methods

2009-01-06 Thread Matt Mower
On Tue, Jan 6, 2009 at 9:55 AM, Eloy Duran wrote: > on pure objc classes. It would remove the method and replace it with a > stub which raises a NoMethodError. This may be a naive question but.. would it not be more appropriate to trigger the method_missing functionality? m/ -- Matt Mower :: h

Re: [MacRuby-devel] Warnings about removing methods

2009-01-06 Thread Eloy Duran
I have discussed this with Laurent and will post the results here for completeness. The problem with the objc runtime is that if a method were to be removed and is called from the objc runtime, it would lead to seg faults. Therefor the warning is raised, so people don't have to look through

[MacRuby-devel] [MacRuby] #197: A removed, or undefined, pure Objective-C method should raise a NoMethodError when called.

2009-01-06 Thread MacRuby
#197: A removed, or undefined, pure Objective-C method should raise a NoMethodError when called. -+-- Reporter: eloy.de.en...@… | Owner: lsansone...@… Type: enhancement | Status