Hi Frank,
On Feb 12, 2010, at 7:12 AM, Frank Illenberger wrote:
> Hi there,
>
> today I updated my MacRuby installation from MacRuby 0.5b1 to 0.5 final.
> Sadly, this broke my class "MERStandard" which used a Set.
> My Cocoa app embeds the MacRuby.framework. I initialized an empty set like
> t
Hi Jordan,
On Feb 12, 2010, at 11:12 AM, Jordan K. Hubbard wrote:
> That's definitely a good start, yes, though I must confess to not quite
> understanding the dispatch.fork example?
All Dispatch.fork does is allow you to access the return value of the block
(whenever it is available), either s
That's definitely a good start, yes, though I must confess to not quite
understanding the dispatch.fork example?
On Feb 12, 2010, at 10:20 AM, Ernest N. Prabhakar, Ph.D. wrote:
> Note that this requires the latest nightly to work, as I redid the semantics
> of Dispatch.group.
>
> Fairly minima
Hi Jordan,
On Feb 10, 2010, at 12:30 AM, Jordan K. Hubbard wrote:
> P.S. Is it just me, or do other people have a really hard time turning specs
> into usage-case examples when they read them?
In answer to your plea, I've not only commented up the Dispatch module with
examples:
http://svn.mac
Hi there,
today I updated my MacRuby installation from MacRuby 0.5b1 to 0.5 final. Sadly,
this broke my class "MERStandard" which used a Set.
My Cocoa app embeds the MacRuby.framework. I initialized an empty set like
this, which worked fine with MacRuby 0.5b1
mySet = Set.new
With MacRuby 0.5 f
