/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 61 by nigel, Sat Feb 24 21:39:58 2007 UTC revision 67 by nigel, Sat Feb 24 21:40:13 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 3.0 02-Jan-02  Version 4.2 14-Apr-03
5    ---------------------
6    
7    1. Typo "#if SUPPORT_UTF8" instead of "#ifdef SUPPORT_UTF8" fixed.
8    
9    2. Changes to the building process, supplied by Ronald Landheer-Cieslak
10         [ON_WINDOWS]: new variable, "#" on non-Windows platforms
11         [NOT_ON_WINDOWS]: new variable, "#" on Windows platforms
12         [WIN_PREFIX]: new variable, "cyg" for Cygwin
13         * Makefile.in: use autoconf substitution for OBJEXT, EXEEXT, BUILD_OBJEXT
14           and BUILD_EXEEXT
15         Note: automatic setting of the BUILD variables is not yet working
16         set CPPFLAGS and BUILD_CPPFLAGS (but don't use yet) - should be used at
17           compile-time but not at link-time
18         [LINK]: use for linking executables only
19         make different versions for Windows and non-Windows
20         [LINKLIB]: new variable, copy of UNIX-style LINK, used for linking
21           libraries
22         [LINK_FOR_BUILD]: new variable
23         [OBJEXT]: use throughout
24         [EXEEXT]: use throughout
25         <winshared>: new target
26         <wininstall>: new target
27         <dftables.o>: use native compiler
28         <dftables>: use native linker
29         <install>: handle Windows platform correctly
30         <clean>: ditto
31         <check>: ditto
32         copy DLL to top builddir before testing
33    
34       As part of these changes, -no-undefined was removed again. This was reported
35       to give trouble on HP-UX 11.0, so getting rid of it seems like a good idea
36       in any case.
37    
38    3. Some tidies to get rid of compiler warnings:
39    
40       . In the match_data structure, match_limit was an unsigned long int, whereas
41         match_call_count was an int. I've made them both unsigned long ints.
42    
43       . In pcretest the fact that a const uschar * doesn't automatically cast to
44         a void * provoked a warning.
45    
46       . Turning on some more compiler warnings threw up some "shadow" variables
47         and a few more missing casts.
48    
49    4. If PCRE was complied with UTF-8 support, but called without the PCRE_UTF8
50       option, a class that contained a single character with a value between 128
51       and 255 (e.g. /[\xFF]/) caused PCRE to crash.
52    
53    5. If PCRE was compiled with UTF-8 support, but called without the PCRE_UTF8
54       option, a class that contained several characters, but with at least one
55       whose value was between 128 and 255 caused PCRE to crash.
56    
57    
58    Version 4.1 12-Mar-03
59    ---------------------
60    
61    1. Compiling with gcc -pedantic found a couple of places where casts were
62    needed, and a string in dftables.c that was longer than standard compilers are
63    required to support.
64    
65    2. Compiling with Sun's compiler found a few more places where the code could
66    be tidied up in order to avoid warnings.
67    
68    3. The variables for cross-compiling were called HOST_CC and HOST_CFLAGS; the
69    first of these names is deprecated in the latest Autoconf in favour of the name
70    CC_FOR_BUILD, because "host" is typically used to mean the system on which the
71    compiled code will be run. I can't find a reference for HOST_CFLAGS, but by
72    analogy I have changed it to CFLAGS_FOR_BUILD.
73    
74    4. Added -no-undefined to the linking command in the Makefile, because this is
75    apparently helpful for Windows. To make it work, also added "-L. -lpcre" to the
76    linking step for the pcreposix library.
77    
78    5. PCRE was failing to diagnose the case of two named groups with the same
79    name.
80    
81    6. A problem with one of PCRE's optimizations was discovered. PCRE remembers a
82    literal character that is needed in the subject for a match, and scans along to
83    ensure that it is present before embarking on the full matching process. This
84    saves time in cases of nested unlimited repeats that are never going to match.
85    Problem: the scan can take a lot of time if the subject is very long (e.g.
86    megabytes), thus penalizing straightforward matches. It is now done only if the
87    amount of subject to be scanned is less than 1000 bytes.
88    
89    7. A lesser problem with the same optimization is that it was recording the
90    first character of an anchored pattern as "needed", thus provoking a search
91    right along the subject, even when the first match of the pattern was going to
92    fail. The "needed" character is now not set for anchored patterns, unless it
93    follows something in the pattern that is of non-fixed length. Thus, it still
94    fulfils its original purpose of finding quick non-matches in cases of nested
95    unlimited repeats, but isn't used for simple anchored patterns such as /^abc/.
96    
97    
98    Version 4.0 17-Feb-03
99    ---------------------
100    
101    1. If a comment in an extended regex that started immediately after a meta-item
102    extended to the end of string, PCRE compiled incorrect data. This could lead to
103    all kinds of weird effects. Example: /#/ was bad; /()#/ was bad; /a#/ was not.
104    
105    2. Moved to autoconf 2.53 and libtool 1.4.2.
106    
107    3. Perl 5.8 no longer needs "use utf8" for doing UTF-8 things. Consequently,
108    the special perltest8 script is no longer needed - all the tests can be run
109    from a single perltest script.
110    
111    4. From 5.004, Perl has not included the VT character (0x0b) in the set defined
112    by \s. It has now been removed in PCRE. This means it isn't recognized as
113    whitespace in /x regexes too, which is the same as Perl. Note that the POSIX
114    class [:space:] *does* include VT, thereby creating a mess.
115    
116    5. Added the class [:blank:] (a GNU extension from Perl 5.8) to match only
117    space and tab.
118    
119    6. Perl 5.005 was a long time ago. It's time to amalgamate the tests that use
120    its new features into the main test script, reducing the number of scripts.
121    
122    7. Perl 5.8 has changed the meaning of patterns like /a(?i)b/. Earlier versions
123    were backward compatible, and made the (?i) apply to the whole pattern, as if
124    /i were given. Now it behaves more logically, and applies the option setting
125    only to what follows. PCRE has been changed to follow suit. However, if it
126    finds options settings right at the start of the pattern, it extracts them into
127    the global options, as before. Thus, they show up in the info data.
128    
129    8. Added support for the \Q...\E escape sequence. Characters in between are
130    treated as literals. This is slightly different from Perl in that $ and @ are
131    also handled as literals inside the quotes. In Perl, they will cause variable
132    interpolation. Note the following examples:
133    
134        Pattern            PCRE matches      Perl matches
135    
136        \Qabc$xyz\E        abc$xyz           abc followed by the contents of $xyz
137        \Qabc\$xyz\E       abc\$xyz          abc\$xyz
138        \Qabc\E\$\Qxyz\E   abc$xyz           abc$xyz
139    
140    For compatibility with Perl, \Q...\E sequences are recognized inside character
141    classes as well as outside them.
142    
143    9. Re-organized 3 code statements in pcretest to avoid "overflow in
144    floating-point constant arithmetic" warnings from a Microsoft compiler. Added a
145    (size_t) cast to one statement in pcretest and one in pcreposix to avoid
146    signed/unsigned warnings.
147    
148    10. SunOS4 doesn't have strtoul(). This was used only for unpicking the -o
149    option for pcretest, so I've replaced it by a simple function that does just
150    that job.
151    
152    11. pcregrep was ending with code 0 instead of 2 for the commands "pcregrep" or
153    "pcregrep -".
154    
155    12. Added "possessive quantifiers" ?+, *+, ++, and {,}+ which come from Sun's
156    Java package. This provides some syntactic sugar for simple cases of what my
157    documentation calls "once-only subpatterns". A pattern such as x*+ is the same
158    as (?>x*). In other words, if what is inside (?>...) is just a single repeated
159    item, you can use this simplified notation. Note that only makes sense with
160    greedy quantifiers. Consequently, the use of the possessive quantifier forces
161    greediness, whatever the setting of the PCRE_UNGREEDY option.
162    
163    13. A change of greediness default within a pattern was not taking effect at
164    the current level for patterns like /(b+(?U)a+)/. It did apply to parenthesized
165    subpatterns that followed. Patterns like /b+(?U)a+/ worked because the option
166    was abstracted outside.
167    
168    14. PCRE now supports the \G assertion. It is true when the current matching
169    position is at the start point of the match. This differs from \A when the
170    starting offset is non-zero. Used with the /g option of pcretest (or similar
171    code), it works in the same way as it does for Perl's /g option. If all
172    alternatives of a regex begin with \G, the expression is anchored to the start
173    match position, and the "anchored" flag is set in the compiled expression.
174    
175    15. Some bugs concerning the handling of certain option changes within patterns
176    have been fixed. These applied to options other than (?ims). For example,
177    "a(?x: b c )d" did not match "XabcdY" but did match "Xa b c dY". It should have
178    been the other way round. Some of this was related to change 7 above.
179    
180    16. PCRE now gives errors for /[.x.]/ and /[=x=]/ as unsupported POSIX
181    features, as Perl does. Previously, PCRE gave the warnings only for /[[.x.]]/
182    and /[[=x=]]/. PCRE now also gives an error for /[:name:]/ because it supports
183    POSIX classes only within a class (e.g. /[[:alpha:]]/).
184    
185    17. Added support for Perl's \C escape. This matches one byte, even in UTF8
186    mode. Unlike ".", it always matches newline, whatever the setting of
187    PCRE_DOTALL. However, PCRE does not permit \C to appear in lookbehind
188    assertions. Perl allows it, but it doesn't (in general) work because it can't
189    calculate the length of the lookbehind. At least, that's the case for Perl
190    5.8.0 - I've been told they are going to document that it doesn't work in
191    future.
192    
193    18. Added an error diagnosis for escapes that PCRE does not support: these are
194    \L, \l, \N, \P, \p, \U, \u, and \X.
195    
196    19. Although correctly diagnosing a missing ']' in a character class, PCRE was
197    reading past the end of the pattern in cases such as /[abcd/.
198    
199    20. PCRE was getting more memory than necessary for patterns with classes that
200    contained both POSIX named classes and other characters, e.g. /[[:space:]abc/.
201    
202    21. Added some code, conditional on #ifdef VPCOMPAT, to make life easier for
203    compiling PCRE for use with Virtual Pascal.
204    
205    22. Small fix to the Makefile to make it work properly if the build is done
206    outside the source tree.
207    
208    23. Added a new extension: a condition to go with recursion. If a conditional
209    subpattern starts with (?(R) the "true" branch is used if recursion has
210    happened, whereas the "false" branch is used only at the top level.
211    
212    24. When there was a very long string of literal characters (over 255 bytes
213    without UTF support, over 250 bytes with UTF support), the computation of how
214    much memory was required could be incorrect, leading to segfaults or other
215    strange effects.
216    
217    25. PCRE was incorrectly assuming anchoring (either to start of subject or to
218    start of line for a non-DOTALL pattern) when a pattern started with (.*) and
219    there was a subsequent back reference to those brackets. This meant that, for
220    example, /(.*)\d+\1/ failed to match "abc123bc". Unfortunately, it isn't
221    possible to check for precisely this case. All we can do is abandon the
222    optimization if .* occurs inside capturing brackets when there are any back
223    references whatsoever. (See below for a better fix that came later.)
224    
225    26. The handling of the optimization for finding the first character of a
226    non-anchored pattern, and for finding a character that is required later in the
227    match were failing in some cases. This didn't break the matching; it just
228    failed to optimize when it could. The way this is done has been re-implemented.
229    
230    27. Fixed typo in error message for invalid (?R item (it said "(?p").
231    
232    28. Added a new feature that provides some of the functionality that Perl
233    provides with (?{...}). The facility is termed a "callout". The way it is done
234    in PCRE is for the caller to provide an optional function, by setting
235    pcre_callout to its entry point. Like pcre_malloc and pcre_free, this is a
236    global variable. By default it is unset, which disables all calling out. To get
237    the function called, the regex must include (?C) at appropriate points. This
238    is, in fact, equivalent to (?C0), and any number <= 255 may be given with (?C).
239    This provides a means of identifying different callout points. When PCRE
240    reaches such a point in the regex, if pcre_callout has been set, the external
241    function is called. It is provided with data in a structure called
242    pcre_callout_block, which is defined in pcre.h. If the function returns 0,
243    matching continues; if it returns a non-zero value, the match at the current
244    point fails. However, backtracking will occur if possible. [This was changed
245    later and other features added - see item 49 below.]
246    
247    29. pcretest is upgraded to test the callout functionality. It provides a
248    callout function that displays information. By default, it shows the start of
249    the match and the current position in the text. There are some new data escapes
250    to vary what happens:
251    
252        \C+         in addition, show current contents of captured substrings
253        \C-         do not supply a callout function
254        \C!n        return 1 when callout number n is reached
255        \C!n!m      return 1 when callout number n is reached for the mth time
256    
257    30. If pcregrep was called with the -l option and just a single file name, it
258    output "<stdin>" if a match was found, instead of the file name.
259    
260    31. Improve the efficiency of the POSIX API to PCRE. If the number of capturing
261    slots is less than POSIX_MALLOC_THRESHOLD, use a block on the stack to pass to
262    pcre_exec(). This saves a malloc/free per call. The default value of
263    POSIX_MALLOC_THRESHOLD is 10; it can be changed by --with-posix-malloc-threshold
264    when configuring.
265    
266    32. The default maximum size of a compiled pattern is 64K. There have been a
267    few cases of people hitting this limit. The code now uses macros to handle the
268    storing of links as offsets within the compiled pattern. It defaults to 2-byte
269    links, but this can be changed to 3 or 4 bytes by --with-link-size when
270    configuring. Tests 2 and 5 work only with 2-byte links because they output
271    debugging information about compiled patterns.
272    
273    33. Internal code re-arrangements:
274    
275    (a) Moved the debugging function for printing out a compiled regex into
276        its own source file (printint.c) and used #include to pull it into
277        pcretest.c and, when DEBUG is defined, into pcre.c, instead of having two
278        separate copies.
279    
280    (b) Defined the list of op-code names for debugging as a macro in
281        internal.h so that it is next to the definition of the opcodes.
282    
283    (c) Defined a table of op-code lengths for simpler skipping along compiled
284        code. This is again a macro in internal.h so that it is next to the
285        definition of the opcodes.
286    
287    34. Added support for recursive calls to individual subpatterns, along the
288    lines of Robin Houston's patch (but implemented somewhat differently).
289    
290    35. Further mods to the Makefile to help Win32. Also, added code to pcregrep to
291    allow it to read and process whole directories in Win32. This code was
292    contributed by Lionel Fourquaux; it has not been tested by me.
293    
294    36. Added support for named subpatterns. The Python syntax (?P<name>...) is
295    used to name a group. Names consist of alphanumerics and underscores, and must
296    be unique. Back references use the syntax (?P=name) and recursive calls use
297    (?P>name) which is a PCRE extension to the Python extension. Groups still have
298    numbers. The function pcre_fullinfo() can be used after compilation to extract
299    a name/number map. There are three relevant calls:
300    
301      PCRE_INFO_NAMEENTRYSIZE        yields the size of each entry in the map
302      PCRE_INFO_NAMECOUNT            yields the number of entries
303      PCRE_INFO_NAMETABLE            yields a pointer to the map.
304    
305    The map is a vector of fixed-size entries. The size of each entry depends on
306    the length of the longest name used. The first two bytes of each entry are the
307    group number, most significant byte first. There follows the corresponding
308    name, zero terminated. The names are in alphabetical order.
309    
310    37. Make the maximum literal string in the compiled code 250 for the non-UTF-8
311    case instead of 255. Making it the same both with and without UTF-8 support
312    means that the same test output works with both.
313    
314    38. There was a case of malloc(0) in the POSIX testing code in pcretest. Avoid
315    calling malloc() with a zero argument.
316    
317    39. Change 25 above had to resort to a heavy-handed test for the .* anchoring
318    optimization. I've improved things by keeping a bitmap of backreferences with
319    numbers 1-31 so that if .* occurs inside capturing brackets that are not in
320    fact referenced, the optimization can be applied. It is unlikely that a
321    relevant occurrence of .* (i.e. one which might indicate anchoring or forcing
322    the match to follow \n) will appear inside brackets with a number greater than
323    31, but if it does, any back reference > 31 suppresses the optimization.
324    
325    40. Added a new compile-time option PCRE_NO_AUTO_CAPTURE. This has the effect
326    of disabling numbered capturing parentheses. Any opening parenthesis that is
327    not followed by ? behaves as if it were followed by ?: but named parentheses
328    can still be used for capturing (and they will acquire numbers in the usual
329    way).
330    
331    41. Redesigned the return codes from the match() function into yes/no/error so
332    that errors can be passed back from deep inside the nested calls. A malloc
333    failure while inside a recursive subpattern call now causes the
334    PCRE_ERROR_NOMEMORY return instead of quietly going wrong.
335    
336    42. It is now possible to set a limit on the number of times the match()
337    function is called in a call to pcre_exec(). This facility makes it possible to
338    limit the amount of recursion and backtracking, though not in a directly
339    obvious way, because the match() function is used in a number of different
340    circumstances. The count starts from zero for each position in the subject
341    string (for non-anchored patterns). The default limit is, for compatibility, a
342    large number, namely 10 000 000. You can change this in two ways:
343    
344    (a) When configuring PCRE before making, you can use --with-match-limit=n
345        to set a default value for the compiled library.
346    
347    (b) For each call to pcre_exec(), you can pass a pcre_extra block in which
348        a different value is set. See 45 below.
349    
350    If the limit is exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
351    
352    43. Added a new function pcre_config(int, void *) to enable run-time extraction
353    of things that can be changed at compile time. The first argument specifies
354    what is wanted and the second points to where the information is to be placed.
355    The current list of available information is:
356    
357      PCRE_CONFIG_UTF8
358    
359    The output is an integer that is set to one if UTF-8 support is available;
360    otherwise it is set to zero.
361    
362      PCRE_CONFIG_NEWLINE
363    
364    The output is an integer that it set to the value of the code that is used for
365    newline. It is either LF (10) or CR (13).
366    
367      PCRE_CONFIG_LINK_SIZE
368    
369    The output is an integer that contains the number of bytes used for internal
370    linkage in compiled expressions. The value is 2, 3, or 4. See item 32 above.
371    
372      PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
373    
374    The output is an integer that contains the threshold above which the POSIX
375    interface uses malloc() for output vectors. See item 31 above.
376    
377      PCRE_CONFIG_MATCH_LIMIT
378    
379    The output is an unsigned integer that contains the default limit of the number
380    of match() calls in a pcre_exec() execution. See 42 above.
381    
382    44. pcretest has been upgraded by the addition of the -C option. This causes it
383    to extract all the available output from the new pcre_config() function, and to
384    output it. The program then exits immediately.
385    
386    45. A need has arisen to pass over additional data with calls to pcre_exec() in
387    order to support additional features. One way would have been to define
388    pcre_exec2() (for example) with extra arguments, but this would not have been
389    extensible, and would also have required all calls to the original function to
390    be mapped to the new one. Instead, I have chosen to extend the mechanism that
391    is used for passing in "extra" data from pcre_study().
392    
393    The pcre_extra structure is now exposed and defined in pcre.h. It currently
394    contains the following fields:
395    
396      flags         a bitmap indicating which of the following fields are set
397      study_data    opaque data from pcre_study()
398      match_limit   a way of specifying a limit on match() calls for a specific
399                      call to pcre_exec()
400      callout_data  data for callouts (see 49 below)
401    
402    The flag bits are also defined in pcre.h, and are
403    
404      PCRE_EXTRA_STUDY_DATA
405      PCRE_EXTRA_MATCH_LIMIT
406      PCRE_EXTRA_CALLOUT_DATA
407    
408    The pcre_study() function now returns one of these new pcre_extra blocks, with
409    the actual study data pointed to by the study_data field, and the
410    PCRE_EXTRA_STUDY_DATA flag set. This can be passed directly to pcre_exec() as
411    before. That is, this change is entirely upwards-compatible and requires no
412    change to existing code.
413    
414    If you want to pass in additional data to pcre_exec(), you can either place it
415    in a pcre_extra block provided by pcre_study(), or create your own pcre_extra
416    block.
417    
418    46. pcretest has been extended to test the PCRE_EXTRA_MATCH_LIMIT feature. If a
419    data string contains the escape sequence \M, pcretest calls pcre_exec() several
420    times with different match limits, until it finds the minimum value needed for
421    pcre_exec() to complete. The value is then output. This can be instructive; for
422    most simple matches the number is quite small, but for pathological cases it
423    gets very large very quickly.
424    
425    47. There's a new option for pcre_fullinfo() called PCRE_INFO_STUDYSIZE. It
426    returns the size of the data block pointed to by the study_data field in a
427    pcre_extra block, that is, the value that was passed as the argument to
428    pcre_malloc() when PCRE was getting memory in which to place the information
429    created by pcre_study(). The fourth argument should point to a size_t variable.
430    pcretest has been extended so that this information is shown after a successful
431    pcre_study() call when information about the compiled regex is being displayed.
432    
433    48. Cosmetic change to Makefile: there's no need to have / after $(DESTDIR)
434    because what follows is always an absolute path. (Later: it turns out that this
435    is more than cosmetic for MinGW, because it doesn't like empty path
436    components.)
437    
438    49. Some changes have been made to the callout feature (see 28 above):
439    
440    (i)  A callout function now has three choices for what it returns:
441    
442           0  =>  success, carry on matching
443         > 0  =>  failure at this point, but backtrack if possible
444         < 0  =>  serious error, return this value from pcre_exec()
445    
446         Negative values should normally be chosen from the set of PCRE_ERROR_xxx
447         values. In particular, returning PCRE_ERROR_NOMATCH forces a standard
448         "match failed" error. The error number PCRE_ERROR_CALLOUT is reserved for
449         use by callout functions. It will never be used by PCRE itself.
450    
451    (ii) The pcre_extra structure (see 45 above) has a void * field called
452         callout_data, with corresponding flag bit PCRE_EXTRA_CALLOUT_DATA. The
453         pcre_callout_block structure has a field of the same name. The contents of
454         the field passed in the pcre_extra structure are passed to the callout
455         function in the corresponding field in the callout block. This makes it
456         easier to use the same callout-containing regex from multiple threads. For
457         testing, the pcretest program has a new data escape
458    
459           \C*n        pass the number n (may be negative) as callout_data
460    
461         If the callout function in pcretest receives a non-zero value as
462         callout_data, it returns that value.
463    
464    50. Makefile wasn't handling CFLAGS properly when compiling dftables. Also,
465    there were some redundant $(CFLAGS) in commands that are now specified as
466    $(LINK), which already includes $(CFLAGS).
467    
468    51. Extensions to UTF-8 support are listed below. These all apply when (a) PCRE
469    has been compiled with UTF-8 support *and* pcre_compile() has been compiled
470    with the PCRE_UTF8 flag. Patterns that are compiled without that flag assume
471    one-byte characters throughout. Note that case-insensitive matching applies
472    only to characters whose values are less than 256. PCRE doesn't support the
473    notion of cases for higher-valued characters.
474    
475    (i)   A character class whose characters are all within 0-255 is handled as
476          a bit map, and the map is inverted for negative classes. Previously, a
477          character > 255 always failed to match such a class; however it should
478          match if the class was a negative one (e.g. [^ab]). This has been fixed.
479    
480    (ii)  A negated character class with a single character < 255 is coded as
481          "not this character" (OP_NOT). This wasn't working properly when the test
482          character was multibyte, either singly or repeated.
483    
484    (iii) Repeats of multibyte characters are now handled correctly in UTF-8
485          mode, for example: \x{100}{2,3}.
486    
487    (iv)  The character escapes \b, \B, \d, \D, \s, \S, \w, and \W (either
488          singly or repeated) now correctly test multibyte characters. However,
489          PCRE doesn't recognize any characters with values greater than 255 as
490          digits, spaces, or word characters. Such characters always match \D, \S,
491          and \W, and never match \d, \s, or \w.
492    
493    (v)   Classes may now contain characters and character ranges with values
494          greater than 255. For example: [ab\x{100}-\x{400}].
495    
496    (vi)  pcregrep now has a --utf-8 option (synonym -u) which makes it call
497          PCRE in UTF-8 mode.
498    
499    52. The info request value PCRE_INFO_FIRSTCHAR has been renamed
500    PCRE_INFO_FIRSTBYTE because it is a byte value. However, the old name is
501    retained for backwards compatibility. (Note that LASTLITERAL is also a byte
502    value.)
503    
504    53. The single man page has become too large. I have therefore split it up into
505    a number of separate man pages. These also give rise to individual HTML pages;
506    these are now put in a separate directory, and there is an index.html page that
507    lists them all. Some hyperlinking between the pages has been installed.
508    
509    54. Added convenience functions for handling named capturing parentheses.
510    
511    55. Unknown escapes inside character classes (e.g. [\M]) and escapes that
512    aren't interpreted therein (e.g. [\C]) are literals in Perl. This is now also
513    true in PCRE, except when the PCRE_EXTENDED option is set, in which case they
514    are faulted.
515    
516    56. Introduced HOST_CC and HOST_CFLAGS which can be set in the environment when
517    calling configure. These values are used when compiling the dftables.c program
518    which is run to generate the source of the default character tables. They
519    default to the values of CC and CFLAGS. If you are cross-compiling PCRE,
520    you will need to set these values.
521    
522    57. Updated the building process for Windows DLL, as provided by Fred Cox.
523    
524    
525    Version 3.9 02-Jan-02
526  ---------------------  ---------------------
527    
528  1. A bit of extraneous text had somehow crept into the pcregrep documentation.  1. A bit of extraneous text had somehow crept into the pcregrep documentation.

Legend:
Removed from v.61  
changed lines
  Added in v.67

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12