[Ironruby-core] Initializing external Ruby libraries
michael.letterle at gmail.com
Wed Feb 13 20:53:27 EST 2008
Yes, my only point is that the way it works today a .NET class becomes
a Ruby class and a .NET method becomes a Ruby method. Nothing is
stopping one from writing a .NET assembly so that it "feels" like Ruby
when it's compiled.
That said, I can see the advantage of being able to use the RubyClass
and RubyMethod attributes outside of that..
Is the performance between this and utilizing an Initializer that great?
On Feb 13, 2008 8:13 PM, John Messerly <jomes at microsoft.com> wrote:
> Michael Letterle:
> > What do you see would be the advantage of something like this as
> > opposed to the current method of loading .NET assemblies? I mean you
> > could use something like OpenSSL.NET
> > (http://openssl-net.sourceforge.net/) today to implement ssl in
> > IronRuby for example
> The main reason for implementing the libraries in C# would be for better performance. But if it's just a thin wrapper on top of some .NET piece, there's no reason you couldn't implement it in Ruby code instead of C#
> - John
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
More information about the Ironruby-core