From: sera@... (Francis Hwang)
Date: 2004-01-30T21:39:53+09:00
Subject: Re: Ruby and Perl Integration

Well, it would be one more option, wouldn't it? Right now you have two
choices: 1. Rewrite the functionality in a new Ruby library, or 2. Use
Perl. This would introduce a new in-between option. Nobody should be
forced to port code simply as a matter of principle.

I should say also, that one of the things that Ruby gives you as the
power to re-imagine how your library interface should look. If you're
going to design something that externally looks exactly like a Perl
library, then maybe there's not much point in re-writing it anyway.

Francis

ptkwt@aracnet.com (Phil Tomson) wrote in message news:<bvcn471jq2@enews3.newsguy.com>...

> Perhaps, but I suspect that if it worked well enough that no one would 
> find the time to rewrite the code in Ruby.  It could actually be 
> counterproductive.  People would just figure that well we can just grab 
> the Perl module Foo::Bar and use it with the Perl_eval thingy and nobody 
> would bother to actually translate Foo::Bar to Ruby and 'rubyfy' it.
> 
> ...Not saying that you shouldn't try to make a bridge between the two 
> languages just saying that this could be a consequence.
> 
> Phil