[ruby-talk:7994] Re: defined? problem?

Kevin Smith <[e-mail]> writes:

> I guess another 'convenience' that is confusing 
> things is allowing if-modifiers after the code, 
> which I still don't like. I won't use them in my 
> code, and this is yet another reason.

I kind-of agree. But there are times when I find modifiers are
genuinely the most natural means of expressing an idea:

  puts resultCode  if $debugging

or

  successMsg.write unless errorOccurred


The guide I use is fairly simple: the condition shouldn't be a
critical part of the program logic, and the statement that's being
modified should be simple.It's a trade-off: conciseness can both
help and hinder readability.

Now if you want real testosterone-loaded statement modifiers, how
about

   if a > 99
     puts "one"
   else
     puts "two"
   end unless b < 10

   while c < 5
     c += 1
   end if c > 2

and

    while a < 10
      a += 1
      puts a
    end while (a = gets.to_i) > 0


Regards


Dave