From: bbense+comp.lang.ruby.Jan.23.03@... Date: 2003-01-24T09:25:50+09:00 Subject: Re: Automating Perl -> Ruby translation? -----BEGIN PGP SIGNED MESSAGE----- In article <043001c2be89$0819c9e0$0300a8c0@austin.rr.com>, Hal E. Fulton wrote: >----- Original Message ----- >From: "Daniel Carrera" >To: "ruby-talk ML" >Sent: Friday, January 17, 2003 2:13 PM >Subject: Re: Automating Perl -> Ruby translation? > > >> Seriously, I'm sure that this is possible, but I'm not sure it's worth >> it. It might be better to translate CPAN to Ruby. Unfortunatelly, nearly >> all of CPAN is written with XS, which is a Perl-only tool. I don't know >> how hard it'd be to translate XS to SWIG, but my experience is that XS is >> quite complicated. - - Huh? SWIG is a way to hide XS from yourself. > >Well, I'd settle for a very crude tool. > >I once translated a small Perl program >(200 lines or so) with the help of some >others. > >You'd be surprised how much progress I >made just by saying :%s/my $//g in vi. > >I'm joking less than you think. Eight or >nine such commands, and the Perl was >starting to look a lot like Ruby. > >As for XS: I don't know what it is. - - Consider yourself very lucky. IMHO, it's the big reason to prefer Ruby over Perl. The Ruby C API is a joy compared to XS. > >Anyway, it's just a thought. > >I do have two or three things I want >to translate. If I had a tool, I would >use it, and others might also. > - - Your only chance is to trick Simon into using his magic B modules to accomplish this for you. - - Booker C. Bense -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBPjCDmWTWTAjn5N/lAQF04AQAt4VjYjp0XbUJhfGAskLak4Mso3meB1fr NHCTlgJuNcDviTQfrs6tMtOjgqQGpBeqKW9MvqbLZ8LHdBS6zYNxR2Pm2/Cgr7cX l/iocvQ1bFPzO+ZucUbBdytIiX8K/pIzoEqb9gOzOULTlkjOo/14WMzII6iMKLq9 a3864bDkbjA= =ABO2 -----END PGP SIGNATURE-----