From: "Volkmann, Mark" Date: 2002-04-30T07:53:38+09:00 Subject: RE: Source File/Class relationship - the Ruby way This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1EFD0.7D113400 Content-Type: text/plain; charset="iso-8859-1" I'm also coming to Ruby from Java. I have to admit that I find it frustrating when I'm trying to find the code for a class called Foo and it's not in a file called Foo.rb! It seems that there is a convention where files names are all lowercase, so the class Foo would be defined in a file called foo.rb. > -----Original Message----- > From: David Corbin [mailto:dcorbin@imperitek.com] > Sent: Monday, April 29, 2002 5:46 PM > To: ruby-talk@ruby-lang.org > Subject: Source File/Class relationship - the Ruby way > > > I come from the Java world, and I have tendancy to write one class to > one file. With a similar name. And to have the directory structure > mirror the module structure. Also, though I'm seldom very good about > it, I strive for many classes with small methods and small > method count. > But, I'm starting to suspect this is making my life much > more complex > than it needs to be. > > Is there an accepted Ruby standard on this issue? If so, where can I > read about it? *********************************************************************************** WARNING: All e-mail sent to and from this address will be received or otherwise recorded by the A.G. Edwards corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. ************************************************************************************ ------_=_NextPart_001_01C1EFD0.7D113400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Source File/Class relationship - the Ruby way

I'm also coming to Ruby from Java.  I have to admit = that I find it frustrating when I'm trying to find the code for a class cal= led Foo and it's not in a file called Foo.rb!  It seems that there is = a convention where files names are all lowercase, so the class Foo would be= defined in a file called foo.rb.

> -----Original Message-----
> From: David Corbin [mailto:dcorbin@imperitek.com]
> Sent: Monday, April 29, 2002 5:46 PM
> To: ruby-talk@ruby-lang.org
> Subject: Source File/Class relationship - the Ruby = way
>
>
> I come from the Java world, and I have tendancy to = write one class to
> one file.  With a similar name.  And to h= ave the directory structure
> mirror the module structure.  Also, though I'm= seldom very good about
> it, I strive for many classes with small methods an= d small
> method count.
>  But, I'm starting to suspect this is making m= y life much
> more complex
> than it needs to be.
>
> Is there an accepted Ruby standard on this issue?&n= bsp; If so, where can I
> read about it?



***************************************************************************= ********
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************= *********
 ------_=_NextPart_001_01C1EFD0.7D113400--