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

Diff of /code/trunk/ChangeLog

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

revision 207 by ph10, Mon Aug 6 09:32:14 2007 UTC revision 349 by ph10, Wed Jul 2 18:42:11 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 8.0 02 Jul-08
5    ---------------------
6    
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
13    
14    
15    Version 7.7 07-May-08
16    ---------------------
17    
18    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
19        a string to a long long, pretend we don't even have a long long." This is
20        done by checking for the strtoq, strtoll, and _strtoi64 functions.
21    
22    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
23        pre-7.6 versions, which defined a global no_arg variable instead of putting
24        it in the RE class. (See also #8 below.)
25    
26    3.  Remove a line of dead code, identified by coverity and reported by Nuno
27        Lopes.
28    
29    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
30    
31        (1) The include/exclude patterns were being applied to the whole pathnames
32            of files, instead of just to the final components.
33    
34        (2) If there was more than one level of directory, the subdirectories were
35            skipped unless they satisfied the include/exclude conditions. This is
36            inconsistent with GNU grep (and could even be seen as contrary to the
37            pcregrep specification - which I improved to make it absolutely clear).
38            The action now is always to scan all levels of directory, and just
39            apply the include/exclude patterns to regular files.
40    
41    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
42        --exclude_dir in the tests to avoid scanning .svn directories.
43    
44    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
45        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
46        doesn't support NULs in patterns.
47    
48    7.  Added some missing "const"s to declarations of static tables in
49        pcre_compile.c and pcre_dfa_exec.c.
50    
51    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
52        caused by fix #2  above. (Subsequently also a second patch to fix the
53        first patch. And a third patch - this was a messy problem.)
54    
55    9.  Applied Craig's patch to remove the use of push_back().
56    
57    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
58        matching function regexec().
59    
60    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
61        which, however, unlike Perl's \g{...}, are subroutine calls, not back
62        references. PCRE supports relative numbers with this syntax (I don't think
63        Oniguruma does).
64    
65    12. Previously, a group with a zero repeat such as (...){0} was completely
66        omitted from the compiled regex. However, this means that if the group
67        was called as a subroutine from elsewhere in the pattern, things went wrong
68        (an internal error was given). Such groups are now left in the compiled
69        pattern, with a new opcode that causes them to be skipped at execution
70        time.
71    
72    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
73        to the way PCRE behaves:
74    
75        (a) A lone ] character is dis-allowed (Perl treats it as data).
76    
77        (b) A back reference to an unmatched subpattern matches an empty string
78            (Perl fails the current match path).
79    
80        (c) A data ] in a character class must be notated as \] because if the
81            first data character in a class is ], it defines an empty class. (In
82            Perl it is not possible to have an empty class.) The empty class []
83            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
84            The negative empty class [^] matches any one character, independently
85            of the DOTALL setting.
86    
87    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
88        non-existent subpattern following a character class starting with ']' and
89        containing () gave an internal compiling error instead of "reference to
90        non-existent subpattern". Fortunately, when the pattern did exist, the
91        compiled code was correct. (When scanning forwards to check for the
92        existencd of the subpattern, it was treating the data ']' as terminating
93        the class, so got the count wrong. When actually compiling, the reference
94        was subsequently set up correctly.)
95    
96    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
97        it was being rejected as not supported by pcre_dfa_exec(), even though
98        other assertions are supported. I have made pcre_dfa_exec() support
99        (*FAIL).
100    
101    16. The implementation of 13c above involved the invention of a new opcode,
102        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
103        cannot be changed at match time, I realized I could make a small
104        improvement to matching performance by compiling OP_ALLANY instead of
105        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
106        on the OP_ANY path.
107    
108    17. Compiling pcretest on Windows with readline support failed without the
109        following two fixes: (1) Make the unistd.h include conditional on
110        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
111    
112    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
113        ncurses library to be included for pcretest when ReadLine support is
114        requested, but also to allow for it to be overridden. This patch came from
115        Daniel Bergström.
116    
117    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
118        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
119        any errors with the current Unicode tables. Thanks to Peter Kankowski for
120        spotting this.
121    
122    
123    Version 7.6 28-Jan-08
124    ---------------------
125    
126    1.  A character class containing a very large number of characters with
127        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
128        overflow.
129    
130    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
131        HAVE_LONG_LONG is not defined.
132    
133    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
134        bring them up to date and include new features. This patch includes:
135    
136        - Fixed PH's badly added libz and libbz2 support.
137        - Fixed a problem with static linking.
138        - Added pcredemo. [But later removed - see 7 below.]
139        - Fixed dftables problem and added an option.
140        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
141            HAVE_LONG_LONG.
142        - Added readline support for pcretest.
143        - Added an listing of the option settings after cmake has run.
144    
145    4.  A user submitted a patch to Makefile that makes it easy to create
146        "pcre.dll" under mingw when using Configure/Make. I added stuff to
147        Makefile.am that cause it to include this special target, without
148        affecting anything else. Note that the same mingw target plus all
149        the other distribution libraries and programs are now supported
150        when configuring with CMake (see 6 below) instead of with
151        Configure/Make.
152    
153    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
154        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
155        exported in the Windows port". It has not yet been confirmed that the patch
156        solves the problem, but it does no harm.
157    
158    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
159        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
160        with CMake, and also correct the comment about stack recursion.
161    
162    7.  Remove the automatic building of pcredemo from the ./configure system and
163        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
164        of a program that users should build themselves after PCRE is installed, so
165        building it automatically is not really right. What is more, it gave
166        trouble in some build environments.
167    
168    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
169    
170    
171    Version 7.5 10-Jan-08
172    ---------------------
173    
174    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
175        values in parens when parsing an RE using the C++ wrapper."
176    
177    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
178        Characters greater than 255 were excluded from the class instead of being
179        included.
180    
181    3.  The same bug as (2) above applied to negated POSIX classes such as
182        [:^space:].
183    
184    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
185        defined or documented. It seems to have been a typo for PCRE_STATIC, so
186        I have changed it.
187    
188    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
189        first named subpattern) and a construct such as (?&a) would reference the
190        first named subpattern whose name started with "a" (in other words, the
191        length check was missing). Both these problems are fixed. "Subpattern name
192        expected" is now given for (?&) (a zero-length name), and this patch also
193        makes it give the same error for \k'' (previously it complained that that
194        was a reference to a non-existent subpattern).
195    
196    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
197        this is right because (?- can be followed by option settings as well as by
198        digits. I have, however, made the messages clearer.
199    
200    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
201        than the number used in the conditional) now cause a compile-time error.
202        This is actually not compatible with Perl, which accepts such patterns, but
203        treats the conditional as always being FALSE (as PCRE used to), but it
204        seems to me that giving a diagnostic is better.
205    
206    8.  Change "alphameric" to the more common word "alphanumeric" in comments
207        and messages.
208    
209    9.  Fix two occurrences of "backslash" in comments that should have been
210        "backspace".
211    
212    10. Remove two redundant lines of code that can never be obeyed (their function
213        was moved elsewhere).
214    
215    11. The program that makes PCRE's Unicode character property table had a bug
216        which caused it to generate incorrect table entries for sequences of
217        characters that have the same character type, but are in different scripts.
218        It amalgamated them into a single range, with the script of the first of
219        them. In other words, some characters were in the wrong script. There were
220        thirteen such cases, affecting characters in the following ranges:
221    
222          U+002b0 - U+002c1
223          U+0060c - U+0060d
224          U+0061e - U+00612
225          U+0064b - U+0065e
226          U+0074d - U+0076d
227          U+01800 - U+01805
228          U+01d00 - U+01d77
229          U+01d9b - U+01dbf
230          U+0200b - U+0200f
231          U+030fc - U+030fe
232          U+03260 - U+0327f
233          U+0fb46 - U+0fbb1
234          U+10450 - U+1049d
235    
236    12. The -o option (show only the matching part of a line) for pcregrep was not
237        compatible with GNU grep in that, if there was more than one match in a
238        line, it showed only the first of them. It now behaves in the same way as
239        GNU grep.
240    
241    13. If the -o and -v options were combined for pcregrep, it printed a blank
242        line for every non-matching line. GNU grep prints nothing, and pcregrep now
243        does the same. The return code can be used to tell if there were any
244        non-matching lines.
245    
246    14. Added --file-offsets and --line-offsets to pcregrep.
247    
248    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
249        infinitely looping recursion. The bug was that positive lookaheads were not
250        being skipped when checking for a possible empty match (negative lookaheads
251        and both kinds of lookbehind were skipped).
252    
253    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
254        inclusion of <windows.h> to before rather than after the definition of
255        INVALID_FILE_ATTRIBUTES (patch from David Byron).
256    
257    17. Specifying a possessive quantifier with a specific limit for a Unicode
258        character property caused pcre_compile() to compile bad code, which led at
259        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
260        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
261        caused the error; without that there was no problem.
262    
263    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
264    
265    19. Added --enable-pcretest-libreadline.
266    
267    20. In pcrecpp.cc, the variable 'count' was incremented twice in
268        RE::GlobalReplace(). As a result, the number of replacements returned was
269        double what it should be. I removed one of the increments, but Craig sent a
270        later patch that removed the other one (the right fix) and added unit tests
271        that check the return values (which was not done before).
272    
273    21. Several CMake things:
274    
275        (1) Arranged that, when cmake is used on Unix, the libraries end up with
276            the names libpcre and libpcreposix, not just pcre and pcreposix.
277    
278        (2) The above change means that pcretest and pcregrep are now correctly
279            linked with the newly-built libraries, not previously installed ones.
280    
281        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
282    
283    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
284        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
285        UTF-8 newline character). The key issue is that the pattern starts .*;
286        this means that the match must be either at the beginning, or after a
287        newline. The bug was in the code for advancing after a failed match and
288        checking that the new position followed a newline. It was not taking
289        account of UTF-8 characters correctly.
290    
291    23. PCRE was behaving differently from Perl in the way it recognized POSIX
292        character classes. PCRE was not treating the sequence [:...:] as a
293        character class unless the ... were all letters. Perl, however, seems to
294        allow any characters between [: and :], though of course it rejects as
295        unknown any "names" that contain non-letters, because all the known class
296        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
297        for example, whereas PCRE did not - it did not recognize a POSIX character
298        class. This seemed a bit dangerous, so the code has been changed to be
299        closer to Perl. The behaviour is not identical to Perl, because PCRE will
300        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
301        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
302        Perl does, and where it didn't before.
303    
304    24. Rewrite so as to remove the single use of %n from pcregrep because in some
305        Windows environments %n is disabled by default.
306    
307    
308    Version 7.4 21-Sep-07
309    ---------------------
310    
311    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
312        means that a class such as [\s] counted as "explicit reference to CR or
313        LF". That isn't really right - the whole point of the change was to try to
314        help when there was an actual mention of one of the two characters. So now
315        the change happens only if \r or \n (or a literal CR or LF) character is
316        encountered.
317    
318    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
319        of both had grown to the point where there were only 3 bits left.
320        Fortunately, there was spare space in the data structure, and so I have
321        moved the internal flags into a new 16-bit field to free up more option
322        bits.
323    
324    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
325        but did not set the internal JCHANGED flag - either of these is enough to
326        control the way the "get" function works - but the PCRE_INFO_JCHANGED
327        facility is supposed to tell if (?J) was ever used, so now (?J) at the
328        start sets both bits.
329    
330    4.  Added options (at build time, compile time, exec time) to change \R from
331        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
332    
333    5.  doc/pcresyntax.html was missing from the distribution.
334    
335    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
336        compatibility, even though it is no longer used.
337    
338    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
339        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
340        windows.h file is present (where different names are used). [This was
341        reversed later after testing - see 16 below.]
342    
343    8.  Changed all #include <config.h> to #include "config.h". There were also
344        some further <pcre.h> cases that I changed to "pcre.h".
345    
346    9.  When pcregrep was used with the --colour option, it missed the line ending
347        sequence off the lines that it output.
348    
349    10. It was pointed out to me that arrays of string pointers cause lots of
350        relocations when a shared library is dynamically loaded. A technique of
351        using a single long string with a table of offsets can drastically reduce
352        these. I have refactored PCRE in four places to do this. The result is
353        dramatic:
354    
355          Originally:                          290
356          After changing UCP table:            187
357          After changing error message table:   43
358          After changing table of "verbs"       36
359          After changing table of Posix names   22
360    
361        Thanks to the folks working on Gregex for glib for this insight.
362    
363    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
364        unicode-properties was also set.
365    
366    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
367    
368    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
369        checked only for CRLF.
370    
371    14. Added casts to pcretest.c to avoid compiler warnings.
372    
373    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
374    
375    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
376        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
377        entirely. This removes changes made in 7 above.
378    
379    17. The CMake files have been updated, and there is now more information about
380        building with CMake in the NON-UNIX-USE document.
381    
382    
383    Version 7.3 28-Aug-07
384  ---------------------  ---------------------
385    
386   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 64  Version 7.3 05-Jul-07 Line 443  Version 7.3 05-Jul-07
443      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
444      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
445      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
446    
447  10. Fixed a bug in the documentation for get/copy named substring when  10. Fixed a bug in the documentation for get/copy named substring when
448      duplicate names are permitted. If none of the named substrings are set, the      duplicate names are permitted. If none of the named substrings are set, the
449      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
450      empty string.      empty string.
451    
452  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
453      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
454      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
455      terminating ] is not found. PCRE has been made compatible with Perl in this      terminating ] is not found. PCRE has been made compatible with Perl in this
456      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
457      cause memory overwriting.      cause memory overwriting.
458    
459  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
460      string has been matched (to stop an infinite loop). It was not recognizing      string has been matched (to stop an infinite loop). It was not recognizing
461      a conditional subpattern that could match an empty string if that      a conditional subpattern that could match an empty string if that
462      subpattern was within another subpattern. For example, it looped when      subpattern was within another subpattern. For example, it looped when
463      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
464      condition was not nested. This bug has been fixed.      condition was not nested. This bug has been fixed.
465    
466  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
467      past the start of the subject in the presence of bytes with the top bit      past the start of the subject in the presence of bytes with the top bit
468      set, for example "\x8aBCD".      set, for example "\x8aBCD".
469    
470    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
471        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
472    
473    14. Optimized (?!) to (*FAIL).
474    
475    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
476        This restricts code points to be within the range 0 to 0x10FFFF, excluding
477        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
478        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
479        does: it's just the validity check that is more restrictive.
480    
481    16. Inserted checks for integer overflows during escape sequence (backslash)
482        processing, and also fixed erroneous offset values for syntax errors during
483        backslash processing.
484    
485    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
486        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
487    
488    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
489        caused an overrun.
490    
491    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
492        something other than just ASCII characters) inside a group that had an
493        unlimited repeat caused a loop at compile time (while checking to see
494        whether the group could match an empty string).
495    
496    20. Debugging a pattern containing \p or \P could cause a crash. For example,
497        [\P{Any}] did so. (Error in the code for printing property names.)
498    
499    21. An orphan \E inside a character class could cause a crash.
500    
501    22. A repeated capturing bracket such as (A)? could cause a wild memory
502        reference during compilation.
503    
504    23. There are several functions in pcre_compile() that scan along a compiled
505        expression for various reasons (e.g. to see if it's fixed length for look
506        behind). There were bugs in these functions when a repeated \p or \P was
507        present in the pattern. These operators have additional parameters compared
508        with \d, etc, and these were not being taken into account when moving along
509        the compiled data. Specifically:
510    
511        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
512            length.
513    
514        (b) An item such as \pL+ within a repeated group could cause crashes or
515            loops.
516    
517        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
518            "reference to non-existent subpattern" error.
519    
520        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
521    
522    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
523        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
524    
525    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
526    
527    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
528        character were causing crashes (broken optimization).
529    
530    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
531        \p or \P) caused a compile-time loop.
532    
533    28. More problems have arisen in unanchored patterns when CRLF is a valid line
534        break. For example, the unstudied pattern [\r\n]A does not match the string
535        "\r\nA" because change 7.0/46 below moves the current point on by two
536        characters after failing to match at the start. However, the pattern \nA
537        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
538        the same is true. There doesn't seem any very clean way out of this, but
539        what I have chosen to do makes the common cases work: PCRE now takes note
540        of whether there can be an explicit match for \r or \n anywhere in the
541        pattern, and if so, 7.0/46 no longer applies. As part of this change,
542        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
543        pattern has explicit CR or LF references.
544    
545    29. Added (*CR) etc for changing newline setting at start of pattern.
546    
547    
548  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
549  ---------------------  ---------------------

Legend:
Removed from v.207  
changed lines
  Added in v.349

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12