From: azrael@...
Date: 2006-04-13T22:31:24+09:00
Subject: Re: Equivalent of Java static code block in Ruby?

> >
> > Why?  Why add MORE syntax to solve a non-problem?  This would also require
> you to put all you attr_* calls in this new syntax, as well as calls to
> private :method.  I vote (as if it would matter ;) ) for documentation being
> written, not new syntax.

Maybe it's a Javaism that's deeply engrained in my consciousness, but I
think of the top-level class block to be for declarations and
initialization of members belonging to the class, not random "executive" code, per se.

By putting class-load-time execution into some kind of static constructor, it
cleans up that division of responsibility a bit, and produces a
marginally more literate bunch of code.

Martin