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

Diff of /code/trunk/ChangeLog

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

revision 7 by nigel, Sat Feb 24 21:38:09 2007 UTC revision 19 by nigel, Sat Feb 24 21:38:33 2007 UTC
# Line 2  ChangeLog for PCRE Line 2  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    
5    Version 1.08 27-Mar-98
6    ----------------------
7    
8    1. Add PCRE_UNGREEDY to invert the greediness of quantifiers.
9    
10    2. Add (?U) and (?X) to set PCRE_UNGREEDY and PCRE_EXTRA respectively. The
11    latter must appear before anything that relies on it in the pattern.
12    
13    
14    Version 1.07 16-Feb-98
15    ----------------------
16    
17    1. A pattern such as /((a)*)*/ was not being diagnosed as in error (unlimited
18    repeat of a potentially empty string).
19    
20    
21    Version 1.06 23-Jan-98
22    ----------------------
23    
24    1. Added Markus Oberhumer's little patches for C++.
25    
26    2. Literal strings longer than 255 characters were broken.
27    
28    
29    Version 1.05 23-Dec-97
30    ----------------------
31    
32    1. Negated character classes containing more than one character were failing if
33    PCRE_CASELESS was set at run time.
34    
35    
36    Version 1.04 19-Dec-97
37    ----------------------
38    
39    1. Corrected the man page, where some "const" qualifiers had been omitted.
40    
41    2. Made debugging output print "{0,xxx}" instead of just "{,xxx}" to agree with
42    input syntax.
43    
44    3. Fixed memory leak which occurred when a regex with back references was
45    matched with an offsets vector that wasn't big enough. The temporary memory
46    that is used in this case wasn't being freed if the match failed.
47    
48    4. Tidied pcretest to ensure it frees memory that it gets.
49    
50    5. Temporary memory was being obtained in the case where the passed offsets
51    vector was exactly big enough.
52    
53    6. Corrected definition of offsetof() from change 5 below.
54    
55    7. I had screwed up change 6 below and broken the rules for the use of
56    setjmp(). Now fixed.
57    
58    
59    Version 1.03 18-Dec-97
60    ----------------------
61    
62    1. A erroneous regex with a missing opening parenthesis was correctly
63    diagnosed, but PCRE attempted to access brastack[-1], which could cause crashes
64    on some systems.
65    
66    2. Replaced offsetof(real_pcre, code) by offsetof(real_pcre, code[0]) because
67    it was reported that one broken compiler failed on the former because "code" is
68    also an independent variable.
69    
70    3. The erroneous regex a[]b caused an array overrun reference.
71    
72    4. A regex ending with a one-character negative class (e.g. /[^k]$/) did not
73    fail on data ending with that character. (It was going on too far, and checking
74    the next character, typically a binary zero.) This was specific to the
75    optimized code for single-character negative classes.
76    
77    5. Added a contributed patch from the TIN world which does the following:
78    
79      + Add an undef for memmove, in case the the system defines a macro for it.
80    
81      + Add a definition of offsetof(), in case there isn't one. (I don't know
82        the reason behind this - offsetof() is part of the ANSI standard - but
83        it does no harm).
84    
85      + Reduce the ifdef's in pcre.c using macro DPRINTF, thereby eliminating
86        most of the places where whitespace preceded '#'. I have given up and
87        allowed the remaining 2 cases to be at the margin.
88    
89      + Rename some variables in pcre to eliminate shadowing. This seems very
90        pedantic, but does no harm, of course.
91    
92    6. Moved the call to setjmp() into its own function, to get rid of warnings
93    from gcc -Wall, and avoided calling it at all unless PCRE_EXTRA is used.
94    
95    7. Constructs such as \d{8,} were compiling into the equivalent of
96    \d{8}\d{0,65527} instead of \d{8}\d* which didn't make much difference to the
97    outcome, but in this particular case used more store than had been allocated,
98    which caused the bug to be discovered because it threw up an internal error.
99    
100    8. The debugging code in both pcre and pcretest for outputting the compiled
101    form of a regex was going wrong in the case of back references followed by
102    curly-bracketed repeats.
103    
104    
105  Version 1.02 12-Dec-97  Version 1.02 12-Dec-97
106  ----------------------  ----------------------
107    

Legend:
Removed from v.7  
changed lines
  Added in v.19

  ViewVC Help
Powered by ViewVC 1.1.5