[ruby-talk:02210] Re: parse bug in 1.5

"Conrad Schneiker" <[e-mail]> writes:

> Well, however this issue is resolved, maybe "always use parens" (in
> the sorts of contexts we have been discussing) should be something
> that a Ruby "strict mode" should require, and maybe verbose mode
> should always warn about it.

FWIW, in the book we're recommending that people use parens, but...

I don't think you could make it mandatory without drastically changing 
the feel of the language.

  class Address
    attr :zip,true
  end
  a = Address.new
  a.zip = 76654
  p a.zip

would become

  class Address
    attr(:zip, true)
  end
  a = Address.new()
  a.zip = 76654
  p(a.zip())

Which looks different, and messier, to my eyes.



Dave