barjunk wrote:
> Francis Cianfrocca wrote:
> > On 8/17/06, Daniel Berger <djberg96 / gmail.com> wrote:
> > > Francis Cianfrocca wrote:
> > > > On 8/16/06, barjunk <barjunk / attglobal.net> wrote:
> > > > > These warnings occurs after the filter line but before the search line.
> > > >>
> > > >> This looks like it is at the lines that have:
> > > >>
> > > >> scanner.scan <someregex>
> > > >>
> > > >> What needs to be done to make those warnings go away?
> > > >
> > > >
> > > > Umm... any feedback, Barjunk? If this is not a real problem, I want to
> > > > rollback the code changes I made.
> > > >
> > > >
> > > They show up if you run with -w.  Personally, I think the parens help
> > > with readability in this case.
> > >
> > > Just my .02.
> > >
> > > Regards,
> > >
> > > Dan
> > >
> > >
> >
> >
> > Got it. Thanks, Dan. I outsmarted myself- I thought about -w (which
> > barjunk mentioned) but instead of testing it the easy way, I added
> > $VERBOSE=true to my test script, and that didn't produce any warnings.
> >
> > The current version in Rubyforge SVN does not give the warnings. I'll
> > hold off another release for a few days in case anything else turns
> > up.
>
> Sorry for the late response...I only get digests and have been busy on
> a project.  I will update to the latest and see what happens.
>
> Mike B.

I don't have an svn client at the moment and not going to be able to
(time wise) be able to get to that any time soon...if you can build a
gem for me, I'll be able to test it easily.  Sorry about that.

Mike B.