Date: Tue, 29 Aug 2000 14:20:12 -0400 (EDT) From: Pavel Roskin <[EMAIL PROTECTED]> I haven't checked the older versions, but this behaviour of GNU grep is weird (it may or may not be a bug, dependent on the standard): $ echo foo |./grep -E ' *+' foo It is not a bug. GNU grep extends the semantics of regular expressions so that 'x*+' is equivalent to '(x*)+'. POSIX does not require that grep -E reject ' *+'; it merely says that the results are undefined. So this behavior of GNU grep is correct even when POSIXLY_CORRECT is set.
- AC_TRY_CPP too strict? (Was: grep -... Pavel Roskin
- Re: AC_TRY_CPP too strict? (Was: gr... Alexandre Oliva
- Re: AC_TRY_CPP too strict? (Was: gr... Pavel Roskin
- Re: AC_TRY_CPP too strict? (Was: gr... Thomas Dickey
- Re: AC_TRY_CPP too strict? (Was: gr... Alexandre Oliva
- Re: grep -E ? (Was: Compilation problem solved) Thomas E. Dickey
- Re: grep -E ? (Was: Compilation problem solved) Alexandre Oliva
- Re: grep -E ? (Was: Compilation problem solv... Thomas E. Dickey
- Re: grep -E ? (Was: Compilation problem ... Pavel Roskin
- Re: grep -E ? (Was: Compilation pro... Thomas E. Dickey
- Re: grep -E ? (Was: Compilation pro... Paul Eggert
- Re: grep -E ? (Was: Compilation pro... Thomas Dickey
- Re: grep -E ? (Was: Compilation pro... Paul Eggert
- Re: grep -E ? (Was: Compilation problem ... Paul Eggert
- Re: grep -E ? (Was: Compilation problem solved) Pavel Roskin
- Re: grep -E ? (Was: Compilation problem solved) Alexandre Oliva
- Re: grep -E ? (Was: Compilation problem solved) Pavel Roskin
- Re: grep -E ? (Was: Compilation problem solv... Alexandre Oliva
- Re: grep -E ? (Was: Compilation problem ... Pavel Roskin
- Re: grep -E ? (Was: Compilation problem solved) Paul Eggert
- Re: grep -E ? (Was: Compilation problem solved) Pavel Roskin