From: "David A. Black" <dblack@...>
Date: 2004-02-21T04:01:09+09:00
Subject: Re: Instance variable capitalization

Hi --

On Sat, 21 Feb 2004, Jim Freeze wrote:

> On Saturday, 21 February 2004 at  0:49:49 +0900, David A. Black wrote:
> > On Fri, 20 Feb 2004, Jim Freeze wrote:
> > 
> > > On Friday, 20 February 2004 at 23:00:58 +0900, David A. Black wrote:
> > > > On Fri, 20 Feb 2004, Jim Freeze wrote:
> > > > 
> > > > You've questioned its ruby-like-ness (correctly, I think), and
> > > > stated that you're not inclined to use it, and that it isn't
> > > > used much.  
> > > > 
> > > > Is there any reason *not* to avoid it? :-)
> > >  
> > > It just bugs me? :)
> > 
> > But surely that's a reason *to* avoid it :-)
> 
> For me, but I don't think that will fly for everyone else
> in the company. I was looking for a more concrete reason.
> 
> Surely you can come up with one David. :)

I'm definitely an advocate of traditional Ruby style, and I like to
use the Ruby source as the arbiter of style.  Not that it's absolutely
uniform, but certain practices, such as avoiding camelCase for
variable method names, are adhered to in the overwhelming majority of
cases.  

For your @Question we find:

$ egrep "(^|[^@])@[[:upper:]]" `find . -name "*.rb"` | wc -l
    186
$ egrep "(^|[^@])@[[:lower:]]" `find . -name "*.rb"` | wc -l
   6438

So it's not unheard of, but it's very rare.  Of the 186 @Upper ones,
about 150 are in irb.  I guess there's some special case or need
there.


David

-- 
David A. Black
dblack@wobblini.net