#196: GVL is held when invoking blocking run-loop related calls
---+
Reporter: peter.ro...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority:
In practice, you should avoid passing objects as context to methods
like this one, because their implementation won't keep a GC
reference to them, so they might disappear during a collection cycle.
Since the Cocoa frameworks are GC-aware, these are generally strong
pointers.
-Ben
I subclassed a Core Data entity Recipe with PPRecipe < NSManaged
object, and created accessors for the fields:
class PPRecipe < NSManagedObject
attr_accessor :name, :desc, :type, :imagePath, :serves
end
but these fields now don't save or display correct after I create
objects, and restart the a
On Jan 4, 2009, at 10:05 PM, peter royal wrote:
however, i'm having trouble making use of them in macruby.
my initial naive attempt was to just throw the .h and .m files into
my project. with this, i got an 'AsyncSocket' class in ruby, but the
selectors defined in the header weren't availabl
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
