procmail
[Top] [All Lists]

Re: MATCH bug?

1998-06-23 08:41:33
Jari Aalto responded to Stan Ryckman,

| I'm sure Phil or David can give "under the hood" explanation, but

Philip knows what's under the hood; all I can comment on is what's in the
trunk.

| my understanding is that this is the stingy vs. greedy race condition
| in the context of \/ operation.
| 
|     From someone(_at_)somewhere(_dot_)com  Fri Jun 19 18:51:56 1998
|                                ==================
| 
|     [^ ]+ +.*\/..:

But there's no chance for stinginess or greediness here; there are no
characters that can allow a choice (such as ?, *, or +).  MATCH should
take in two characters and a colon (or nothing at all if the entire
expression isn't matched).

|         ..:         # The preceding "." regexps match anything

Not anything, but any two non-newline characters, and there have to be
exactly two.  Stan was right: this is a bug.  I've played around a little,
and procmail 3.11pre7 treats   (anything non-null, even .)+.*\/  as
(whatever was plussed)+\/.*  .

<Prev in Thread] Current Thread [Next in Thread>