Tomas's message below seems to reflect what I've been thinking lately. Does anyone else think that in many cases porting C libraries to Ruby or even reusing ports from the Rubinius project would be beneficial to getting more libraries running on IronRuby? I'm supposing that IR performance will continue to improve, and I like the idea of contributing to more than one project (or reusing someone else's work). Is that a good idea? Should we instead wait for FFI on IR? Or is all of this a case-by-case basis approach? I have nothing concrete in mind, atm, I'm just wondering "out loud."
Cheers! Ryan Riley Email: ryan.ri...@panesofglass.org LinkedIn: http://www.linkedin.com/in/ryanriley Blog: http://wizardsofsmart.net/ Twitter: @panesofglass Website: http://panesofglass.org/ On Fri, Nov 27, 2009 at 4:46 PM, Tomas Matousek < tomas.matou...@microsoft.com> wrote: > BTW: Since parts of the OpenSSL library are already written in Ruby (see > ruby-1.8.6p368\lib\ruby\1.8\openssl directory) it might be easier to write > the rest in Ruby as well. With calls to .NET implementation of the > cryptographic algorithms, of course. > If you chose to go that way you can add the scripts to > Merlin\Main\Languages\Ruby\Libs. > > Tomas > > -----Original Message----- > From: ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] On Behalf Of Tomas Matousek > Sent: Friday, November 27, 2009 2:38 PM > To: ironruby-core@rubyforge.org > Subject: Re: [Ironruby-core] handling ruby types and CallSiteStorage in std > library > > It depends whether the method is supposed to invoke Digest's methods > dynamically or not. Does pkcs5_keyivgen method accept any Ruby object that > implements the methods pkcs5_keyivgen calls? Or does it need to be an > instance of Digest class? > If the former is true than you need to use "object" as the parameter type > and use dynamic call sites to invoke those methods. An example of such > dynamic behavior would be MutableStringOps.Compare. If the latter is true > you can just type the parameter to Digest CLR type and call its methods > directly. > > Tomas > > -----Original Message----- > From: ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] On Behalf Of Dylan McClung > Sent: Friday, November 27, 2009 9:34 AM > To: ironruby-core@rubyforge.org > Subject: [Ironruby-core] handling ruby types and CallSiteStorage in std > library > > I'm working on adding code to the OpenSSL extension of the standard library > and I need to understand the design for invoking and typing Ruby code. I > read the 'Modifying the sources' github page and it mentions using > CallSiteStorage to call into Ruby code. > > Specifically, the Cipher ruby class has a dependency on the Digest ruby > classes for the pkcs5_keyivgen method. An optional parameter for this > method is an instance of the Ruby class Digest::Base. How would the type > look, maybe Digest.Digest.Base digest/*optional*/? Or would it be an object > and I'd also need to pass in CallSiteStorage to call methods on the object? > > An example in the standard library of such behavior would be much > appreciated, thanks for any help. > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
