[Rubycocoa-devel 1364] Re: [ANN] MacRuby 0.2

Back to archive index

Pim Snel pim****@linge*****
Tue Jun 10 17:04:14 JST 2008


Thanks, I its clear to me now.

Op 9 jun 2008, om 10:30 heeft Eloy Duran het volgende geschreven:

> Hey Pim,
>
> See http://ruby.macosforge.org/trac/wiki/WhyMacRuby for info on the
> subject.
>
> Cheers,
> Eloy
>
> On Jun 9, 2008, at 10:14 AM, Pim Snel wrote:
>
>> Perhaps a stupid question. But what's the difference between MacRuby
>> and RubyCocoa?
>>
>> Regards,
>> Pim Snel
>>
>> Op 7 jun 2008, om 02:48 heeft Laurent Sansonetti het volgende
>> geschreven:
>>
>>> Hi,
>>>
>>> After 3 months of development, here comes the second release of
>>> MacRuby, 0.2! Check it out while it's still hot!
>>>
>>> MacRuby is a version of Ruby 1.9, ported to run directly on top of
>>> Mac
>>> OS X core technologies such as the Objective-C common runtime and
>>> garbage collector, and the CoreFoundation framework. While still a
>>> work in progress, it is the goal of MacRuby to enable the creation  
>>> of
>>> full-fledged Mac OS X applications which do not sacrifice  
>>> performance
>>> in order to enjoy the benefits of using Ruby.
>>>
>>> You can learn more about MacRuby, and download a binary installer,
>>> from the website:
>>>
>>> http://ruby.macosforge.org
>>>
>>> This is an important release, addressing many bugs, but also
>>> re-implementing parts of the runtime using the CoreFoundation
>>> framework.
>>>
>>> In MacRuby 0.2, all strings, arrays and hashes are now native Cocoa
>>> types, respectively NSString, NSArray and NSDictionary objects. The
>>> entire String, Array and Hash interface was rewritten on top of the
>>> Cocoa equivalents, using the powerful CoreFoundation framework. The
>>> previous implementation, inherited from MRI, is not used anymore.
>>>
>>> The rationale behind this change is simple. It is not necessary
>>> anymore to convert Ruby primitive types to Cocoa, or vice-versa. For
>>> example, a String created in MacRuby can be passed as is, without
>>> conversion, to an underlying C or Objective-C API that expects an
>>> NSString. And vice-versa, any method of the Ruby String class can be
>>> performed on an NSString that comes from Objective-C.
>>>
>>> Enjoy,
>>>
>>> Laurent
>>>
>>> _______________________________________________
>>> Rubycocoa-devel mailing list
>>> Rubyc****@lists*****
>>> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
>>
>> _______________________________________________
>> Rubycocoa-devel mailing list
>> Rubyc****@lists*****
>> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
>
> _______________________________________________
> Rubycocoa-devel mailing list
> Rubyc****@lists*****
> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel




More information about the Rubycocoa-devel mailing list
Back to archive index