summaryrefslogtreecommitdiffstats
path: root/lib/libc/regex
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix computation of the 'n' argument to mbrtowc (through XMBRTOWC) to avoidtjr2004-11-211-4/+4
| | | | | | | | | | reading past 'stop' in various places when converting multibyte characters. Reading too far caused truncation to not be detected when it should have been, eventually causing regexec() to loop infinitely in with certain combinations of patterns and strings in multibyte locales. PR: 74020 MFC after: 4 weeks
* Directly include <runetype.h> for _CurrentRuneLocale, <_ctype.h> doesn'tstefanf2004-10-031-0/+1
| | | | include it in all cases.
* Fix two problems with REG_ICASE that were introduced with the addition oftjr2004-09-051-13/+10
| | | | | | | | | | | multibyte character support: - In CHadd(), avoid writing past the end of the character set bitmap when the opposite-case counterpart of wide characters with values less than NC have values greater than or equal to NC. - In CHaddtype(), fix a braino that caused alphabetic characters to be added to all character classes! (but only with REG_ICASE) PR: 71367
* Update paths to reg*.c and regex2.h. Add a target to build regex.h.tjr2004-07-191-1/+3
|
* Update for removal of cclass.h. Trim some useless targets. Invoke mkhtjr2004-07-191-34/+6
| | | | with "sh mkh" so it works if the script is not executable.
* Update for recent changes to struct re_guts. Disable printing the contentstjr2004-07-191-38/+5
| | | | of OANYOF sets for the moment.
* Remove unused files.tjr2004-07-192-12/+0
|
* Remove an entry from the BUGS section: we have multibyte charactertjr2004-07-121-2/+0
| | | | support now.
* Make regular expression matching aware of multibyte characters. The generaltjr2004-07-125-324/+478
| | | | | | | | | | | | | | | | | idea is that we perform multibyte->wide character conversion while parsing and compiling, then convert byte sequences to wide characters when they're needed for comparison and stepping through the string during execution. As with tr(1), the main complication is to efficiently represent sets of characters in bracket expressions. The old bitmap representation is replaced by a bitmap for the first 256 characters combined with a vector of individual wide characters, a vector of character ranges (for [A-Z] etc.), and a vector of character classes (for [[:alpha:]] etc.). One other point of interest is that although the Boyer-Moore algorithm had to be disabled in the general multibyte case, it is still enabled for UTF-8 because of its self-synchronizing nature. This greatly speeds up matching by reducing the number of multibyte conversions that need to be done.
* Add a new error code, REG_ILLSEQ, to indicate that a regular expressiontjr2004-07-122-1/+5
| | | | contains an illegal multibyte character sequence.
* Remove incomplete support for multi-character collating elements. Removetjr2004-07-112-262/+8
| | | | unused character category calculations.
* Document incorrect handling of multibyte characters.tjr2004-07-061-1/+3
|
* Mechanically kill hard sentence breaks.ru2004-07-022-3/+3
|
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-1/+1
|
* Eliminate 61 warnings emitted at WARNS=2 (leaving 53 to go).nectar2003-02-163-6/+6
| | | | | | | Only warnings that could be fixed without changing the generated object code and without restructuring the source code have been handled. Reviewed by: /sbin/md5
* mdoc(7) police: "The .Fa argument.".ru2002-12-191-2/+6
|
* mdoc(7) police: "The .Fn function".ru2002-12-181-10/+31
|
* libc_r wasn't so tied to libc for 22 months.ru2002-11-181-3/+1
|
* Add restrict type-qualifier.mike2002-10-024-14/+15
|
* Replace various spelling with FALLTHROUGH which is lint()ablecharnier2002-08-251-1/+1
|
* Fix the style of the SCM ID's.obrien2002-03-226-1/+5
| | | | I believe have made all of libc .h's as consistent as possible.
* Fix the style of the SCM ID's.obrien2002-03-226-12/+16
| | | | I believe have made all of libc .c's as consistent as possible.
* Back out last commit (rev 1.2). I thought I caught this file in timeobrien2002-03-221-1/+1
| | | | when deP'ing. But I guess not.
* Remove __P() usage.obrien2002-03-214-54/+54
|
* Remove 'register' keyword.obrien2002-03-218-330/+334
|
* Fix a typo I made in revision 1.5.ru2002-01-221-1/+1
| | | | Submitted by: trevor
* The algorithm that computes the tables used in the BM search algorithm sometimesdcs2001-11-091-1/+2
| | | | | | | | | | access an array beyond it's length. This only happens in the last iteration of a loop, and the value fetched is not used then, so the bug is a relatively innocent one. Fix this by not fetching any value on the last iteration of said loop. Submitted by: MKI <mki@mozone.net> MFC after: 1 week
* mdoc(7) police: Use the new .In macro for #include statements.ru2001-10-011-2/+2
|
* mdoc(7) police: protect trailing full stops of abbreviationsru2001-08-101-1/+1
| | | | with a trailing zero-width space: `e.g.\&'.
* mdoc(7) police:ru2001-08-071-4/+2
| | | | | | | Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text. Not only this slows down the mdoc(7) processing significantly, but it also has an undesired (in this case) effect of disabling hyphenation within the entire enclosed block.
* Remove whitespace at EOL.dd2001-07-151-2/+2
|
* MAN[1-9] -> MAN.ru2001-03-271-2/+2
|
* mdoc(7) police: fixed the weird construct.ru2001-02-091-3/+1
|
* man(7) -> mdoc(7).ru2001-01-121-266/+433
|
* Prepare for mdoc(7)NG.ru2000-12-291-13/+13
|
* Replace a `dagger' sign with a `double dagger' one.ru2000-11-161-15/+15
| | | | The former looks ugly on grotty(1) devices.
* Convert this from -man to -mdoc.ru2000-11-141-140/+345
|
* Actually make it so this Makefile can build grot.green2000-07-101-1/+8
|
* Add a test case for one of the bugs found on the new additions todcs2000-07-091-0/+1
| | | | regex(3).
* Spencer's regex(3) test code.dcs2000-07-098-0/+1727
| | | | Obtained from: BSD/OS
* altoffset() always returned whenever it recursed, because at the enddcs2000-07-091-0/+4
| | | | | | | | | | | | | | of the processing of the recursion, "scan" would be pointing to O_CH (or O_QUEST), which would then be interpreted as being the end character for altoffset(). We avoid this by properly increasing scan before leaving the switch. Without this, something like (a?b?)?cc would result in a g->moffset of 1 instead of 2. I added a case to the soon-to-be-imported regex(3) test code to catch this error.
* Since g->moffset points to the _maximum_ offset at which the mustdcs2000-07-091-1/+1
| | | | | | | | | | | | | string may be found (from the beginning of the pattern), the point at which must is found minus that offset may actually point to some place before the start of the text. In that case, make start = start. Alternatively, this could be tested for in the preceding if, but it did not occur to me. :-) Caught by: regex(3) test code
* Add some casts here and there.dcs2000-07-091-3/+3
|
* Since we have modified charjump to be CHAR_MIN-based, we have todcs2000-07-081-1/+2
| | | | | | correct the offset when we free it. Caught by: phkmalloc
* Do not free NULL pointers.dcs2000-07-071-1/+1
|
* Deal with the signed/unsigned chars issue in a more proper manner. Wedcs2000-07-072-21/+17
| | | | | | | | | use a CHAR_MIN-based array, like elsewhere in the code. Remove a number of unused variables (some due to the above change, one that was left after a number of optimizing steps through the source). Brucified by: bde
* I hate signed chars.^W^W^W^W^WCast to unsigned char before using signeddcs2000-07-061-1/+1
| | | | chars as array indices.
* Correct comment to work with test code.dcs2000-07-061-2/+2
| | | | Prevent out of bounds array access in some specific cases.
* Use UCHAR_MAX consistently.dcs2000-07-061-1/+1
|
* Fix memory leak introduced with regcomp.c rev 1.14.dcs2000-07-021-0/+6
|
OpenPOWER on IntegriCloud