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
Hey Vincent,
Is there a good reason why MacRuby would need to warn the user
about the hazzards of removing methods?
Example:
/Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/
site_ruby/mocha/class_method.rb:50: warning: removing pure
Objective-C method `__stubba__require__stu
Is there a good reason why MacRuby would need to warn the user about
the hazzards of removing methods?
Example:
/Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/
site_ruby/mocha/class_method.rb:50: warning: removing pure Objective-
C method `__stubba__require__stubba__' may caus
Hi,
Is there a good reason why MacRuby would need to warn the user about
the hazzards of removing methods?
Removing methods is always a risky business, also in pure Ruby. But
this is the power that a Ruby user gets and with it comes
responsibility.
And since Ruby doesn't warn for this, MacR
