/[pcre]/code/tags/pcre-1.05/ChangeLog
ViewVC logotype

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

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

  ViewVC Help
Powered by ViewVC 1.1.5