On 25/09/06 Austin Z. said:
- There was only one release of Ruby 1.8.4. There wasn’t even a
security patch (1.8.4.z) released. After release, there are dated
stable snapshots available. It is possible to get a Ruby 1.8.5 that
has further fixes available with recent changes as of right now. But
if you download Ruby 1.8.5, you’re getting ONLY what was released
Core site or not,
points to ruby-doc as it’s standard and core library references. They
shouldn’t do that if they’re not vouching for their authenticity.
I downloaded the 1.8.4 tarball long after it was considered the stable
release, AFAIK. If there was only one release, then I got it. The links
1.8.4 docs should lead one to docs on 1.8.4, yes?
If one goes to http://www.python.org/doc/, you get docs for the latest
that are up-to-date, and maintained by the project itself. More
as you’re likely not using the latest version in production, you can go
http://www.python.org/doc/versions/ and get old versions for your
can also separately browse the in-development versions. It’s always
you are looking at.
Now, if it’s very difficult to keep these up-to-date, then there are
within the Ruby development community to solve, since the tools are
Otherwise, it would be very nice to see the Ruby development community
maintain a model like I’ve referenced here. I constantly find it
get the information that I need to effectively use the language, and I
think that I’m alone.
It’s worth the battle so far, as I am loving the language. Still, the
pickaxe book as an API reference is incomplete. ruby-doc says it’s
1.8.4 but it’s apparently not. There’s a free pickaxe book online from
stream. I get inconsistent results on the code in the tarball from the
tool. This is an exercise in frustration. I have precious little free
time for my own projects, and I don’t want to spend it crawling through
source trying to decipher the API. It’s very difficult to justify my
internally at work when I’m surrounded by Java people who have far
documentation than me.
How can I help this situation? I guess I’ll start by talking to the
ruby-doc, and seeing if I can help.