| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | remove some no-op end of string tests from regex parser•••these are cruft from the original code which used an explicit string
length rather than null termination. i blindly converted all the
checks to null terminator checks, without noticing that in several
cases, the subsequent switch statement would automatically handle the
null byte correctly.
| Rich Felker | 2012-05-13 | 1 | -4/+0 |
| * | another BRE fix: in ^*, * is literal•••i don't understand why this has to be conditional on being in BRE
mode, but enabling this code unconditionally breaks a huge number of
ERE test cases.
| Rich Felker | 2012-05-13 | 1 | -0/+2 |
| * | fix error checking for \ at end of regex (this was broken previously) | Rich Felker | 2012-05-07 | 1 | -1/+1 |
| * | fix copy and paste error in regex code causing mishandling of \) in BRE | Rich Felker | 2012-05-07 | 1 | -1/+1 |
| * | fix regex breakage in last commit (failure to handle empty regex, etc.) | Rich Felker | 2012-05-07 | 1 | -4/+1 |
| * | fix ugly bugs in TRE regex parser•••1. * in BRE is not special at the beginning of the regex or a
subexpression. this broke ncurses' build scripts.
2. \\( in BRE is a literal \ followed by a literal (, not a literal \
followed by a subexpression opener.
3. the ^ in \\(^ in BRE is a literal ^ only at the beginning of the
entire BRE. POSIX allows treating it as an anchor at the beginning of
a subexpression, but TRE's code for checking if it was at the
beginning of a subexpression was wrong, and fixing it for the sake of
supporting a non-portable usage was too much trouble when just
removing this non-portable behavior was much easier.
this patch also moved lots of the ugly logic for empty atom checking
out of the default/literal case and into new cases for the relevant
characters. this should make parsing faster and make the code smaller.
if nothing else it's a lot more readable/logical.
at some point i'd like to revisit and overhaul lots of this code...
| Rich Felker | 2012-05-07 | 1 | -60/+31 |
| * | new fnmatch implementation•••unlike the old one, this one's algorithm does not suffer from
potential stack overflow issues or pathologically bad performance on
certain patterns. instead of backtracking, it uses a matching
algorithm which I have not seen before (unsure whether I invented or
re-invented it) that runs in O(1) space and O(nm) time. it may be
possible to improve the time to O(n), but not without significantly
greater complexity.
| Rich Felker | 2012-04-28 | 1 | -130/+272 |
| * | update fnmatch to POSIX 2008 semantics•••an invalid bracket expression must be treated as if the opening
bracket were just a literal character. this is to fix a bug whereby
POSIX left the behavior of the "[" shell command undefined due to it
being an invalid bracket expression.
| Rich Felker | 2012-04-26 | 1 | -4/+11 |
| * | fix signedness error handling invalid multibyte sequences in regexec•••the "< 0" test was always false due to use of an unsigned type. this
resulted in infinite loops on 32-bit machines (adding -1U to a pointer
is the same as adding -1) and crashes on 64-bit machines (offsetting
the string pointer by 4gb-1b when an illegal sequence was hit).
| Rich Felker | 2012-04-14 | 1 | -2/+2 |
| * | remove invalid code from TRE•••TRE wants to treat + and ? after a +, ?, or * as special; ? means
ungreedy and + is reserved for future use. however, this is
non-conformant. although redundant, these redundant characters have
well-defined (no-op) meaning for POSIX ERE, and are actually _literal_
characters (which TRE is wrongly ignoring) in POSIX BRE mode.
the simplest fix is to simply remove the unneeded nonstandard
functionality. as a plus, this shaves off a small amount of bloat.
| Rich Felker | 2012-04-13 | 1 | -14/+0 |
| * | fix broken regerror (typo) and missing message | Rich Felker | 2012-04-13 | 1 | -2/+2 |
| * | upgrade to latest upstream TRE regex code (0.8.0)•••the main practical results of this change are
1. the regex code is no longer subject to LGPL; it's now 2-clause BSD
2. most (all?) popular nonstandard regex extensions are supported
I hesitate to call this a "sync" since both the old and new code are
heavily modified. in one sense, the old code was "more severely"
modified, in that it was actively hostile to non-strictly-conforming
expressions. on the other hand, the new code has eliminated the
useless translation of the entire regex string to wchar_t prior to
compiling, and now only converts multibyte character literals as
needed.
in the future i may use this modified TRE as a basis for writing the
long-planned new regex engine that will avoid multibyte-to-wide
character conversion entirely by compiling multibyte bracket
expressions specific to UTF-8.
| Rich Felker | 2012-03-20 | 5 | -1155/+1024 |
| * | make glob mark symlinks-to-directories with the GLOB_MARK flag•••POSIX is unclear on whether it should, but all historical
implementations seem to behave this way, and it seems more useful to
applications.
| Rich Felker | 2012-01-23 | 1 | -1/+1 |
| * | support GLOB_PERIOD flag (GNU extension) to glob function•••patch by sh4rm4
| Rich Felker | 2012-01-22 | 1 | -1/+2 |
| * | duplicate re_nsub in LSB/glibc ABI compatible location | Rich Felker | 2011-06-16 | 1 | -1/+1 |
| * | fix handling of d_name in struct dirent•••basically there are 3 choices for how to implement this variable-size
string member:
1. C99 flexible array member: breaks using dirent.h with pre-C99 compiler.
2. old way: length-1 string: generates array bounds warnings in caller.
3. new way: length-NAME_MAX string. no problems, simplifies all code.
of course the usable part in the pointer returned by readdir might be
shorter than NAME_MAX+1 bytes, but that is allowed by the standard and
doesn't hurt anything.
| Rich Felker | 2011-06-06 | 1 | -3/+2 |
| * | safety fix for glob's vla usage: disallow patterns longer than PATH_MAX•••this actually inadvertently disallows some valid patterns with
redundant / or * characters, but it's better than allowing unbounded
vla allocation.
eventually i'll write code to move the pattern to the stack and
eliminate redundancy to ensure that it fits in PATH_MAX at the
beginning of glob. this would also allow it to be modified in place
for passing to fnmatch rather than copied at each level of recursion.
| Rich Felker | 2011-06-05 | 1 | -0/+2 |
| * | eliminate (harmless in this case) vla usage in fnmatch.c | Rich Felker | 2011-06-05 | 1 | -1/+1 |
| * | fix bug in TRE found by clang (typo && instead of &) | Rich Felker | 2011-04-07 | 1 | -1/+1 |
| * | initial check-in, version 0.5.0 | Rich Felker | 2011-02-12 | 7 | -0/+5364 |
