Hi there,
The extlib's #full_const_get will raise an NameError if there's no
constant found. That's what I changed.
I agree that returning nil is more adequate than false though we
should perhaps stay as near to extlib as possible
and raise exceptions to prevent incompatibilities (think of MacRub
I recently shared a MacRuby app with a friend, with MacRuby.framework
included in the .app via a Copy Files target; but the app died on his
machine complaining that /Library/Frameworks/MacRuby.framework wasn't
available. How do I get the app to use the framework in the .app
bundle?
Nic
--
Dr Nic
Hey,
The test looks good to me and I totally agree, false is more
unexpected then nil in this case.
So then I looked up the tests for it from extlib:
http://github.com/sam/extlib/blob/2bc2e8a42c7a49e2e5daf530c29fb2840d0e299d/spec/object_spec.rb#L29
And it doesn't even test for the case that a
Hey,
Attached a patch with the fix. I checked the test and the fix does
indeed make it pass.
In my change I also changed Object#full_const_get to return nil (and
not false) when it does not find a constant because false seemed odd
to me. What do you think?
Cheers
0001-Fixed-HotCocoa-ma
