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

Dave Thomas wrote:
> Conrad Schneiker 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.

I didn't know that 1.5.3. -w would tell you that, but please count me in
the "if people want" group.

BTW, is there a 1.5.3 tarball around somewhere that I overlooked, or do you
just extract from CVS (which I'm not presently familiar with)?

> 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?

We are waiting for the comp.lang.ruby CSV announcement (which should
contain information on voting rules and instructions), which I expect will
be simultaneously posted to news.groups, news.groups.announce,
comp.lang.perl.misc, comp.lang.python, comp.lang.java.programmer, and
comp.lang.misc. Within a day of that happening, I should be following up
with a note here.

Conrad Schneiker
(This note is unofficial and subject to improvement without notice.)