There are modules in CPAN that can do almost anything you need, and
most things that you don’t. Having access to them would make a lot of
Ruby tasks much easier!
May I make a suggestion: Go the route of the Cygwin project. Instead
of porting individual modules, build a bridge that let’s Ruby invoke
and talk to Perl. This would give us free access to (nearly) all of
CPAN. It would also make migrating a lot of Perl apps easier.
Are there any major difficulties it building a Ruby <-> Perl bridge?
Allowing Ruby code to call Perl subroutines, pass vars back and forth,
etc.?
Are there any major difficulties it building a Ruby <-> Perl bridge?
Allowing Ruby code to call Perl subroutines, pass vars back and forth,
etc.?
Horrible, terrible overhead? Personally, I’d be happier to see Parrot
deliver
on the rumours to run all manners of scripts - definately a more
consistent
interoperability solution than making bridges.
Also, porting is useful in that it lets you do API modifications with
respect
to specific Ruby idioms. Although the bridge would let you do a sort of
Ruby
bindings to Perl modules this way more quickly getting rid of recoding
core
algorithms.
Thou shalt study thy libraries and strive not to reinvent them without
cause,
that thy code may be short and readable and thy days pleasant and
productive.
– Seventh commandment for C programmers
CPAN has 9502 modules.
…
So we need a script that will chew on CPAN’s dependency network and
prioritise the CPAN modules.
…
From this principle, all of life and physics may be deduced.
Hi,
(Sorry if this is a duplicate; I attempted to post basically this to
c.l.r before but it hasn’t shown up there or in ruby-talk.)
So, anyway, I couldn’t get Perl’s CPAN::Dependency to do what I wanted,
so I wrote a Ruby script to download CPAN. Well, the names of “releases”
(packages with versions; these can contain multiple modules) and their
authors and dependencies, anyway.
The script downloads about 15000 pages from CPAN, one per author (5000)
plus one per current release (10000), and takes a little while, although
all the pages are small (the per release ones are just Makefile.PL, to
pull prerequisites from). It produces 800k of YAML.
I’ve cleaned up and processed this output (relatively trivially, sorry,
didn’t save my work) to find the top 100 most-required releases. I’ve
got 2 versions of this list: the first is based on CPAN::Dependency’s
notion of only counting authors whose releases refer to each release, to
eliminate false popularity generated by gratuitous references between an
authors own releases. The second isn’t restricted like that and counts a
references for each release that lists it as a prerequisite.
The first that stands out to me, after eliminating functions that exist
or
are being developed in Ruby, is POE - Perl’s event-driven networking
library. It looks quite simple to build, in comparison to Python’s
Twisted,
and it seems it may be possible to build a Twisted-like interface layer
on
top of a POE port. What do Rubyists use in lieu of a Ruby event-driven
networking library?
Would you like to share your lists somewhere (rubygarden’s wiki?) so
that people interested in porting can register their intention, ask for
help, etc.?
authors own releases. The second isn’t restricted like that and counts a
networking library?
Would you like to share your lists somewhere (rubygarden’s wiki?) so
that people interested in porting can register their intention, ask for
help, etc.?
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.