David
Yes? I got an impression it's just matz implementation. BTW, do RubyMotion even
run ruby spec?
—
Sent from Mailbox for iPhone
On Sun, May 19, 2013 at 5:04 AM, david kramf <dakr....@gmail.com> wrote:
> Francis,
> Ruby is very well defined language with a well defined standard.
> David
> On May 17, 2013, at 3:31 PM, Francis Chong wrote:
>> @david depends on your definition on full ruby. I would say standard library
>> is part is full ruby, where RubyMotion deliberately remove part of them
>>
>> @stephen thanks for the update, I should have tested that myself
>> —
>> Sent from Mailbox for iPhone
>>
>>
>> On Fri, May 17, 2013 at 8:26 PM, stephen horne <fat...@gmail.com> wrote:
>>
>> From what I understand, the only thing missing in Rubymotion is eval()
>>
>> There's an article by Clay Allsop about meta-programming in Rubymotion at
>> http://clayallsopp.com/posts/rubymotion-metaprogramming/
>>
>> I tested to see if eval() works in desktop Rubymotion apps (I read somewhere
>> that the reason it's not included is due to Apple restrictions on run-time
>> code evaluation in iOS, rather than a limit of Rubymotion), but it doesn't.
>>
>> fb
>>
>>> <compose-unknown-contact.jpg>
>>> david kramf 17/05/2013 13:19
>>>
>>> Is RubyMotion a full Ruby. Does it support reflection and metaprograming?
>>> Thanks, David Kramf
>>>
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macruby-devel
>>> <postbox-contact.jpg>
>>> Francis Chong 17/05/2013 12:15
>>> While I'm really happy about OS X support on RubyMotion, it is not a
>>> replacement for MacRuby.
>>>
>>> IMHO MacRuby is far superior:
>>>
>>> It offer JIT compiler, you develop orders of magnitude faster as you dont
>>> need clean and rebuild every time.
>>>
>>> You have full ruby compatibility, load standard library as you wish.
>>>
>>> It loads gems and framework dynamically like what you would expected from
>>> regular ruby.
>>>
>>> You don't have to write new gems, or rewrite them. Many gems just work,
>>> even native ones could work.
>>>
>>> You can use regular technique for meta programming, and generally you don't
>>> enter a uncanny valley between dynamic language and static build system.
>>>
>>> Some of these limitations are inherited from RubyMotion due to iOS
>>> restriction, I don't see them going away anytime soon.
>>>
>>> That said, RubyMotion team is the ones who know most of MacRuby, and their
>>> direction is not like MacRuby in past. If you are going to develop Mac app,
>>> your best choice is probably go RubyMotion, or just use Objective-C.
>>> —
>>> Sent from Mailbox for iPhone
>>>
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macruby-devel
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel
