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

[e-mail] writes:

> When I said,
> 
> <<... "always use parens" (in the sorts of contexts we have been
> discussing) ...>>
> 
> above, I probably should have been more explicit and said something more
> like: always use parens in the sorts of cases that tend to be prone to
> misinterpretation or misunderstanding.

Well, perhaps the first thing to do is to collect examples of cases
that are dangerous and look for patterns. I suggest we do this under
1.5.3, using th -w flag, so we don't come up with problems that have
already been fixed. I'll collate the information is people want.

Dave


ps. Conrad: I noticed on news.groups that we now have a vote
taker. Are we just waiting for him to send out the announcement, or is 
this something that we do ourselves?