Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of flester@gmail.com designates
 209.85.212.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGUtCHrKHPKmE_QHGsgQWbB5+UsFZ9K9r_7_Eu58aqEyLCkvBA@mail.gmail.com>
References: 
 <CAP19eqypCNAueE4z6TPU-Jt3g-=L2ptLVo9+c_HC_LVA0LOTog@mail.gmail.com>
 <751586763.199531.1343413258369.JavaMail.root@linzimmb04o.imo.intelink.gov>
 <CADczPYSrO2B1p0yLP+C8FCVkGu_wx0L2ib=cRMCp1aFm7wFgwQ@mail.gmail.com>
 <CAGgKvPkgzdgsWJpuEZEv0L9vY0nbmbzwDzyEG3S1onZ5GnsMWQ@mail.gmail.com>
 <CAGUtCHrKHPKmE_QHGsgQWbB5+UsFZ9K9r_7_Eu58aqEyLCkvBA@mail.gmail.com>
From: Michael Flester <flester@gmail.com>
Date: Sun, 5 Aug 2012 19:16:27 -0400
Message-ID: 
 <CAGgKvPkHOQ0XVeuvobBD-G6tzR2pb-OSkZPjnsT_qEiSvzY+ew@mail.gmail.com>
Subject: Re: egrep usage - 1.3.4
To: user@accumulo.apache.org
Content-Type: multipart/alternative; boundary=bcaec502d8de489b3a04c68cf4eb

--bcaec502d8de489b3a04c68cf4eb
Content-Type: text/plain; charset=UTF-8

Keith --

Switching from match to find should be no change for anyone that is
currently using it.
All patterns that "match" will equally "find". But new users would be able
to take advantage
of not adding the wildcards on both ends.

Mike


On Tue, Jul 31, 2012 at 11:21 AM, Keith Turner <keith@deenlo.com> wrote:

> On Sun, Jul 29, 2012 at 9:47 PM, Michael Flester <flester@gmail.com>
> wrote:
> >
> >
> > On Sat, Jul 28, 2012 at 7:57 PM, John Vines <vines@apache.org> wrote:
> >>
> >> And when dealing with java, it does full matches, so adding the .* to
> >> start and end is necessary.
> >>
> >
> > Java has both Matcher#matches and Matcher#find. The latter would operate
> > more
> > like the egrep(1) command without requiring the wildcards on both ends.
>
> Ah, It should have used the find() call when it was first written.
> Changing it now would be tricky because people who expect the current
> behavior could get unexpected results.  I think we are kinda stuck
> with the current behavior.   Could possibly add an option to use
> find() instead of match().
>

--bcaec502d8de489b3a04c68cf4eb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Keith --<div><br></div><div>Switching from match to find should be no chang=
e for anyone that is currently using it.</div><div>All patterns that &quot;=
match&quot; will equally &quot;find&quot;. But new users would be able to t=
ake advantage</div>

<div>of not adding the wildcards on both ends.</div><div><br></div><div>Mik=
e</div><div><br><br><div class=3D"gmail_quote">On Tue, Jul 31, 2012 at 11:2=
1 AM, Keith Turner <span dir=3D"ltr">&lt;<a href=3D"mailto:keith@deenlo.com=
" target=3D"_blank">keith@deenlo.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On S=
un, Jul 29, 2012 at 9:47 PM, Michael Flester &lt;<a href=3D"mailto:flester@=
gmail.com">flester@gmail.com</a>&gt; wrote:<br>


&gt;<br>
&gt;<br>
&gt; On Sat, Jul 28, 2012 at 7:57 PM, John Vines &lt;<a href=3D"mailto:vine=
s@apache.org">vines@apache.org</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; And when dealing with java, it does full matches, so adding the .*=
 to<br>
&gt;&gt; start and end is necessary.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Java has both Matcher#matches and Matcher#find. The latter would opera=
te<br>
&gt; more<br>
&gt; like the egrep(1) command without requiring the wildcards on both ends=
.<br>
<br>
</div></div>Ah, It should have used the find() call when it was first writt=
en.<br>
Changing it now would be tricky because people who expect the current<br>
behavior could get unexpected results. =C2=A0I think we are kinda stuck<br>
with the current behavior. =C2=A0 Could possibly add an option to use<br>
find() instead of match().<br>
</blockquote></div><br></div>

--bcaec502d8de489b3a04c68cf4eb--