From: Joseph Erickson <jerickson@...>
Date: 2001-12-08T05:02:13+09:00
Subject: [ruby-talk:27845] Re: Perl/Python Module Porting

I just know that I can't use Ruby at work because I can do so much more 
in Perl because of the module support.  If there is an effort to get 
more module support in Ruby, more people may be apt to take it 
seriously.  I love staying up nights programming in this language but if 
I can program in it AND get sleep, I'll be twice as happy. :-)

Should there be a concentrated effort to reuse Perl/Python code in order 
to make Ruby more robust and more attractive to potential corporate 
customers / real world programmers?  Do you guys think this should be a 
focus or should porting be kept on an 'as needed basis'?

-------------------------------
J o s e p h   E r i c k s o n



On Friday, December 7, 2001, at 02:30  PM, Ned Konz wrote:

> On Friday 07 December 2001 11:03 am, Eric Lee Green wrote:
>
>> Only problem with most Perl modules is that they are FAR from being
>> object-oriented. Thus you can't just take a Perl API and port it to 
>> Ruby
>> (with the exception of the very few Perl modules that are 
>> object-oriented).
>
> True... however, this doesn't have to keep you from doing it in Ruby. 
> After
> all, Ruby can deal with non-OO designs as well.
>
> I ported my Perl Algorithm::Diff module to Ruby, as did someone else; 
> this
> wasn't OO (because of compatibility with legacy code based on a prior
> version), but still was an easy port.
>
> My Archive::Zip module is agressively OO, and should be an easy port. 
> I've
> already ported it to Squeak Smalltalk more or less directly.
>
> --
> Ned Konz
> currently: Stanwood, WA
> email:     ned@bike-nomad.com
> homepage:  http://bike-nomad.com
>
>