| 34 |
which uses them. Because the POSIX functions call the native |
which uses them. Because the POSIX functions call the native |
| 35 |
ones, it is also necessary to add -lpcre. |
ones, it is also necessary to add -lpcre. |
| 36 |
|
|
| 37 |
As I am pretty ignorant about POSIX, these functions must be |
I have implemented only those option bits that can be rea- |
| 38 |
considered as experimental. I have implemented only those |
sonably mapped to PCRE native options. In addition, the |
| 39 |
option bits that can be reasonably mapped to PCRE native |
options REG_EXTENDED and REG_NOSUB are defined with the |
| 40 |
options. Other POSIX options are not even defined. It may be |
value zero. They have no effect, but since programs that are |
| 41 |
that it is useful to define, but ignore, other options. |
written to the POSIX interface often use them, this makes it |
| 42 |
Feedback from more knowledgeable folk may cause this kind of |
easier to slot in PCRE as a replacement library. Other POSIX |
| 43 |
detail to change. |
options are not even defined. |
| 44 |
|
|
| 45 |
When PCRE is called via these functions, it is only the API |
When PCRE is called via these functions, it is only the API |
| 46 |
that is POSIX-like in style. The syntax and semantics of the |
that is POSIX-like in style. The syntax and semantics of the |
Parent Directory
| 
Revision Log
| 
Patch