From: Jeremy McAnally <jeremymcanally@...>
Date: 2007-01-10T01:43:12+09:00
Subject: [ANN] Elements of Ruby Style

Hello all,
I'm happy announce a project that I've been working on for a little while.

I've noticed that a lot of posts on the mailing are "what's the most
rubyish way to do (x)?" where x could be transversing a file and
matching regexes to looping through records in a database to switching
between two logic branches.  So, seeing this, I thought, why not give
these people a refernece?  Instead of having to type out a long answer
every time, why not give them a Fine Manual to read?

So I began work on Elements of Ruby: a descriptive style manual, that
is, that this manual will only describe the typical style used in the
language, and should not be used as a way to prescribe style. I want
it to be used as a learning tool and to answer questions about the
best style in a given situation rather than to spawn religious
arguments about style.

The problem is that I havent gotten very far yet (darn you holidays
and book deadlines! ;)).  Actually, that's why I'm posting here: I
need your help.  I've managed to build a small list of items so far
(viewable at http://www.elementsofrubystyle.com/ ), but I want to add
more.  So I thought I would open discussion here for input.  I want it
to be useful to everyone, so everyone should have some input, yes?

I have a Rails applicatio built to power it, but I want to nail down a
fairly final list of things before I populate its database and deploy
it.  After it's deployed, then you will be able to submit comments on
each element (e.g., to voice an exception or add to it) and submit
examples for each one (that will be integrated and properly
attributed) or suggest new things to be added/changed.

Anyhow, look at the list, and let's talk about what should be on there.

Visit http://www.elementsofrubystyle.com/ .

--Jeremy

-- 
My free Ruby e-book:
http://www.humblelittlerubybook.com/book/

My blogs:
http://www.mrneighborly.com/
http://www.rubyinpractice.com/