summaryrefslogtreecommitdiffstats
path: root/lib/libc/regex/regex.3
Commit message (Collapse)AuthorAgeFilesLines
* MFC r300683:pfg2016-06-241-22/+48
| | | | | | | | | | | | | | | | | | | | | | libc: regexec(3) adjustment. Change the behavior of when REG_STARTEND is combined with REG_NOTBOL. From the original posting[1]: "Enable the assumption that pmatch[0].rm_so is a continuation offset to a string and allows us to do a proper assessment of the character in regards to it's word position ('^' or '\<'), without risking going into unallocated memory." This change makes us similar to how glibc handles REG_STARTEND | REG_NOTBOL, and is closely related to a soon-to-land fix to sed. Special thanks to Martijn van Duren and Ingo Schwarze for working out some consistent behaviour. Differential Revision: https://reviews.freebsd.org/D6257 Taken from: openbsd-tech 2016-05-24 [1] (Martijn van Duren)
* Per Regents of the University of Calfornia letter, remove advertisingimp2007-01-091-4/+0
| | | | | | clause. # If I've done so improperly on a file, please let me know.
* Document the fact that word-boundary matching does not worktjr2005-08-171-1/+3
| | | | properly in multibyte locales.
* Expand *n't contractions.ru2005-02-131-3/+3
|
* Sort sections.ru2005-01-201-8/+8
|
* Remove an entry from the BUGS section: we have multibyte charactertjr2004-07-121-2/+0
| | | | support now.
* Add a new error code, REG_ILLSEQ, to indicate that a regular expressiontjr2004-07-121-1/+3
| | | | contains an illegal multibyte character sequence.
* Document incorrect handling of multibyte characters.tjr2004-07-061-1/+3
|
* Mechanically kill hard sentence breaks.ru2004-07-021-2/+2
|
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-1/+1
|
* mdoc(7) police: "The .Fa argument.".ru2002-12-191-2/+6
|
* mdoc(7) police: "The .Fn function".ru2002-12-181-10/+31
|
* Add restrict type-qualifier.mike2002-10-021-7/+8
|
* 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.
* man(7) -> mdoc(7).ru2001-01-121-266/+433
|
* Remove from the notes a bug that it's said to have been fixed.dcs2000-07-021-5/+0
| | | | | | PR: 15561 Submitted by: Martin Kammerhofer <mkamm@gmx.net> Confirmed by: ache
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-121-0/+1
| | | | | | | | | | | | | | | | | track. The $Id$ line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
* Correctly use .Fn instead of .Nm to reference function namesmpp1996-08-221-1/+3
| | | | | | | | in a bunch of man pages. Use the correct .Bx (BSD UNIX) or .At (AT&T UNIX) macros instead of explicitly specifying the version in the text in a bunch of man pages.
* BSD 4.4 Lite Lib Sourcesrgrimes1994-05-271-0/+538
OpenPOWER on IntegriCloud