/[pcre]/code/trunk/doc/pcreposix.3
ViewVC logotype

Diff of /code/trunk/doc/pcreposix.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 41 by nigel, Sat Feb 24 21:39:17 2007 UTC revision 43 by nigel, Sat Feb 24 21:39:21 2007 UTC
# Line 36  can be accessed by adding \fB-lpcreposix Line 36  can be accessed by adding \fB-lpcreposix
36  application which uses them. Because the POSIX functions call the native ones,  application which uses them. Because the POSIX functions call the native ones,
37  it is also necessary to add \fR-lpcre\fR.  it is also necessary to add \fR-lpcre\fR.
38    
39  As I am pretty ignorant about POSIX, these functions must be considered as  I have implemented only those option bits that can be reasonably mapped to PCRE
40  experimental. I have implemented only those option bits that can be reasonably  native options. In addition, the options REG_EXTENDED and REG_NOSUB are defined
41  mapped to PCRE native options. Other POSIX options are not even defined. It may  with the value zero. They have no effect, but since programs that are written
42  be that it is useful to define, but ignore, other options. Feedback from more  to the POSIX interface often use them, this makes it easier to slot in PCRE as
43  knowledgeable folk may cause this kind of detail to change.  a replacement library. Other POSIX options are not even defined.
44    
45  When PCRE is called via these functions, it is only the API that is POSIX-like  When PCRE is called via these functions, it is only the API that is POSIX-like
46  in style. The syntax and semantics of the regular expressions themselves are  in style. The syntax and semantics of the regular expressions themselves are

Legend:
Removed from v.41  
changed lines
  Added in v.43

  ViewVC Help
Powered by ViewVC 1.1.5