|author||Rich Felker <email@example.com>||2013-12-02 02:08:41 -0500|
|committer||Rich Felker <firstname.lastname@example.org>||2013-12-02 02:08:41 -0500|
implement FNM_LEADING_DIR extension flag in fnmatch
previously this flag was defined and accepted as a no-op, possibly breaking some software that uses it. given the choice to remove the definition and possibly break applications that were already working, or simply implement the feature, the latter turned out to be easy enough to make the decision easy. in the case where the FNM_PATHNAME flag is also set, this implementation is clean and essentially optimal. otherwise, it's an inefficient "brute force" implementation. at some point, when cleaning up and refactoring this code, I may add a more direct code path for handling FNM_LEADING_DIR in the non-FNM_PATHNAME case, but at this point my main interest is avoiding introducing new bugs in the code that implements the standard fnmatch features specified by POSIX.
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions