News for hackers. Stuff that matters.
Re:Why I'm Not Using RubyMotion in Production by jevinskie on Wednesday June 26, 2013 @08:52PM (#5950056)
I didn't see a workaround, can you elaborate?
Re:Why I'm Not Using RubyMotion in Production by hboon on Thursday June 27, 2013 @12:00AM (#5950677)
Re:Why I'm Not Using RubyMotion in Production by stashpro on Wednesday June 26, 2013 @08:58PM (#5950067)
I understood that using an instance variable is a viable workaround. Or maybe just code around the issue?
Re:Why I'm Not Using RubyMotion in Production by bobwaycott on Thursday June 27, 2013 @02:12AM (#5950940)
The author states that even using this method has produced indeterminate crashes.
Re:Why I'm Not Using RubyMotion in Production by Legion on Wednesday June 26, 2013 @09:39PM (#5950201)
Read the paragraph that starts with the sentence, "Of course, there's a workaround."
Re:Why I'm Not Using RubyMotion in Production by masukomi on Wednesday June 26, 2013 @10:17PM (#5950368)
you mean the paragraph that includes "...will correct the crashing error – sometimes. I’ve used instance variables and have still experienced crashes in blocks" ? That one? Or was there a paragraph I missed that included a workaround that actually solved the problem rather than minimizing it?