#198: Bug in class constant lookup.
-+--
Reporter: eloy.de.en...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker
#182: The constant lookup in MacRuby does not behave correctly
+---
Reporter: vincent.isamb...@… | Owner: lsansone...@…
Type: defect | Status: new
Pr
#198: Bug in class constant lookup.
-+--
Reporter: eloy.de.en...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
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
#199: Calling super from #respond_to? causes SystemStackError
-+--
Reporter: eloy.de.en...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority:
#198: Bug in class constant lookup.
-+--
Reporter: eloy.de.en...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
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
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
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
#197: A removed, or undefined, pure Objective-C method should raise a
NoMethodError when called.
-+--
Reporter: eloy.de.en...@… | Owner: lsansone...@…
Type: enhancement | Status
10 matches
Mail list logo