[#3109] Is divmod dangerous? — Dave Thomas <Dave@...>

14 messages 2000/06/06

[#3149] Retrieving the hostname and port in net/http — Roland Jesse <jesse@...>

Hi,

12 messages 2000/06/07

[#3222] Ruby coding standard? — Robert Feldt <feldt@...>

16 messages 2000/06/09

[#3277] Re: BUG or something? — Aleksi Niemel<aleksi.niemela@...>

> |I am new to Ruby and this brings up a question I have had

17 messages 2000/06/12
[#3281] Re: BUG or something? — Dave Thomas <Dave@...> 2000/06/12

Aleksi Niemel<aleksi.niemela@cinnober.com> writes:

[#3296] RE: about documentation — Aleksi Niemel<aleksi.niemela@...>

> I want to contribute to the ruby project in my spare time.

15 messages 2000/06/12

[#3407] Waffling between Python and Ruby — "Warren Postma" <embed@...>

I was looking at the Ruby editor/IDE for windows and was disappointed with

19 messages 2000/06/14

[#3410] Exercice: Translate into Ruby :-) — Jilani Khaldi <jilanik@...>

Hi All,

17 messages 2000/06/14

[#3415] Re: Waffling between Python and Ruby — Andrew Hunt <andy@...>

>Static typing..., hmm,...

11 messages 2000/06/14

[#3453] Re: Static Typing( Was: Waffling between Python and Ruby) — Andrew Hunt <andy@...>

32 messages 2000/06/16

[#3516] Deep copy? — Hugh Sasse Staff Elec Eng <hgs@...>

Given that I cannot overload =, how should I go about ensuring a deep

20 messages 2000/06/19

[#3694] Why it's quiet — hal9000@...

We are all busy learning the new language

26 messages 2000/06/29
[#3703] Re: Why it's quiet — "NAKAMURA, Hiroshi" <nahi@...> 2000/06/30

Hi,

[#3705] Re: Why it's quiet — matz@... (Yukihiro Matsumoto) 2000/06/30

Hi,

[ruby-talk:03225] Re: Ruby coding standard?

From: Dave Thomas <Dave@...>
Date: 2000-06-09 15:07:41 UTC
List: ruby-talk #3225
Robert Feldt <feldt@ce.chalmers.se> writes:

> Anyone knows of a Ruby coding standard or at least some recommendations on
> how to write Ruby code that is easily readable? Has some consensus
> evolved?

Have a look at some of the library code. If you feel it's readable,
then copy its style ;-)

I personally use the One True Editor, and Ruby comes with an emacs
mode that lays things out the way _I_ like out of the box (except:
Matz- that last 'do' change means iterators no longer lay out
properly)

One style thing I have evolved towards is attempting to be consistent
in my choice of do/end or {,} for iterators. I've come down in favor
of using {} for single line iterators and do/end for multiline ones:

   a.each { |l| puts l}

   b.each do |line|
     if line.length > 45
       # ...
     else
       # ...
     end
     gurgle(line)
   end

To me, the 'end' in the multiline form echos the 'end' used in ifs,
whiles, and the like.

           end
         end
       end

looks more pleasing than

           end
         }
       end


Regards


Dave

In This Thread