Thanks for sharing Eliott, that seems to be a bug with Xcode and it should
be affecting all 3rd party frameworks, not just MacRuby.
Quite strange, but thanks for showing how you worked around the signing
problem.
- Matt
On Wed, Oct 19, 2011 at 11:23 AM, Elliot Temple wrote:
> http://curi.us/153
I believe someone (Ernie or someone else) did indeed extract some of the
dispatch gem's mixins.
- Matt
On Wed, Oct 19, 2011 at 1:43 PM, Jordan K. Hubbard wrote:
>
> On Oct 19, 2011, at 11:38 AM, Terry Moore wrote:
>
> Yes. But he does state it is a read only not modified array. My
> understandi
Sorry we didn't make more noise about it, but after opening a bug report on
Apple's site and bugging a few people there, they fixed the Xcode bug.
The fix has been in all the recent Xcode beta but we forgot to announce it
when 4.2 was publicly released.
- Matt
On Wed, Oct 19, 2011 at 2:21 PM, ste
In case nobody was watching…
So, today I downloaded Xcode 4.2, hoping IB would recognize outlets and actions
in MacRuby classes. I also downloaded the newest version of MacRuby (0.12) from
the nightly builds.
Now, my outlets and actions (as defined in my Ruby classes) are recognized in
IB. Hur
On Oct 19, 2011, at 11:38 AM, Terry Moore wrote:
> Yes. But he does state it is a read only not modified array. My understanding
> is. 'Array' is an NSMutableArray, I was merely suggesting using freeze to
> throw that exception just in case there maybe some code attempting to
> write/modify.
>
Yes. But he does state it is a read only not modified array. My understanding
is. 'Array' is an NSMutableArray, I was merely suggesting using freeze to throw
that exception just in case there maybe some code attempting to write/modify.
Mutex is the way to go but it also has an overhead.
Terry M
http://curi.us/1538-macruby-and-the-mac-app-store
Got my game in the app store. Hope these notes help others get things working
too.
-- Elliot Temple
http://beginningofinfinity.com/
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
The proper way to protect mutable objects is to use a mutex:
http://www.ruby-doc.org/core-1.9.2/Mutex.html
- Matt
Sent from my iPhone
On Oct 19, 2011, at 8:06, Chuck Remes wrote:
>
> On Oct 19, 2011, at 12:41 AM, Terry Moore wrote:
>
>> If you're not wring/changing the array no problems. Bu
On Oct 19, 2011, at 12:41 AM, Terry Moore wrote:
> If you're not wring/changing the array no problems. But to be safe use
> Object#freeze...
>
> Terry Moore
>
> On 19/10/2011, at 6:26 PM, Michael Johnston wrote:
>
>> Note, in my example I can also guarantee that none of the elements in b are
