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

Diff of /code/trunk/ChangeLog

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

revision 934 by ph10, Sat Feb 25 12:30:36 2012 UTC revision 1334 by ph10, Wed May 15 16:53:18 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.33 28-April-2013
5    --------------------------
6    
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
11    
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
14    
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
18    
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
24    
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
28    
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
31    
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
34    
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
36    
37    9.  Optimizing fast_forward_start_bits in JIT.
38    
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
41    
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
44        (b) Minimum length was not checked before the matching is started.
45    
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
50    
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
54    
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
57    
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
60    
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
62    
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
66    
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
73    
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
75    
76    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
77        gives some modest performance improvement in 8-bit mode.
78    
79    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
80        be expressed in certain programming languages using Universal Character
81        Names.
82    
83    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
84        which points out that "non characters" are not "characters that may not
85        appear in Unicode strings" but rather "characters that are reserved for
86        internal use and have only local meaning".
87    
88    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
89        there was a conditional group that depended on an assertion, if the
90        assertion was false, the callout that immediately followed the alternation
91        in the condition was skipped when pcre_exec() was used for matching.
92    
93    23. Allow an explicit callout to be inserted before an assertion that is the
94        condition for a conditional group, for compatibility with automatic
95        callouts, which always insert a callout at this point.
96    
97    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
98        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
99    
100    25. (*PRUNE) is now supported by the JIT compiler.
101    
102    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
103    
104    27. Fix the case where there are two or more SKIPs with arguments that may be
105        ignored.
106    
107    28. (*SKIP) is now supported by the JIT compiler.
108    
109    29. (*THEN) is now supported by the JIT compiler.
110    
111    30. Update RunTest with additional test selector options.
112    
113    31. The way PCRE handles backtracking verbs has been changed in two ways.
114    
115        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
116        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
117        backtracking. In some cases this makes it more Perl-compatible, but Perl's
118        rather obscure rules do not always do the same thing.
119    
120        (2) Previously, backtracking verbs were confined within assertions. This is
121        no longer the case for positive assertions, except for (*ACCEPT). Again,
122        this sometimes improves Perl compatibility, and sometimes does not.
123    
124    32. A number of tests that were in test 2 because Perl did things differently
125        have been moved to test 1, because either Perl or PCRE has changed, and
126        these tests are now compatible.
127    
128    32. Control verbs are handled in the same way in JIT and interpreter.
129    
130    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
131        contained a forward subroutine reference caused a compile error.
132    
133    34. Auto-detect and optimize limited repetitions in JIT.
134    
135    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
136        blocking (*UTF) etc.
137    
138    36. In the interpreter, maximizing pattern repetitions for characters and
139        character types now use tail recursion, which reduces stack usage.
140    
141    37. The value of the max lookbehind was not correctly preserved if a compiled
142        and saved regex was reloaded on a host of different endianness.
143    
144    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
145        of the compiled pattern block, expand the flags field from 16 to 32 bits
146        because it was almost full.
147    
148    39. Try madvise first before posix_madvise.
149    
150    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
151        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
152        original change locked out all matches of empty strings. This has been
153        changed so that one match of an empty string per line is recognized.
154        Subsequent searches on the same line (for colouring or for --only-matching,
155        for example) do not recognize empty strings.
156    
157    41. Applied a user patch to fix a number of spelling mistakes in comments.
158    
159    42. Data lines longer than 65536 caused pcretest to crash.
160    
161    43. Clarified the data type for length and startoffset arguments for pcre_exec
162        and pcre_dfa_exec in the function-specific man pages, where they were
163        explicitly stated to be in bytes, never having been updated. I also added
164        some clarification to the pcreapi man page.
165    
166    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
167        a segmentation fault.
168    
169    
170    Version 8.32 30-November-2012
171  -----------------------------  -----------------------------
172    
173    1.  Improved JIT compiler optimizations for first character search and single
174        character iterators.
175    
176    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
177        Patch by Daniel Richard G.
178    
179    3.  Single character iterator optimizations in the JIT compiler.
180    
181    4.  Improved JIT compiler optimizations for character ranges.
182    
183    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
184        Reported by Giuseppe D'Angelo.
185    
186    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
187        of a line, was being set incorrectly in cases where .* appeared inside
188        atomic brackets at the start of a pattern, or where there was a subsequent
189        *PRUNE or *SKIP.
190    
191    7.  Improved instruction cache flush for POWER/PowerPC.
192        Patch by Daniel Richard G.
193    
194    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
195        grep:
196    
197        (a) There is now no limit to the number of patterns to be matched.
198    
199        (b) An error is given if a pattern is too long.
200    
201        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
202            are now supported.
203    
204        (d) --exclude-from and --include-from (multiple use) have been added.
205    
206        (e) Exclusions and inclusions now apply to all files and directories, not
207            just to those obtained from scanning a directory recursively.
208    
209        (f) Multiple uses of -f and --file-list are now supported.
210    
211        (g) In a Windows environment, the default for -d has been changed from
212            "read" (the GNU grep default) to "skip", because otherwise the presence
213            of a directory in the file list provokes an error.
214    
215        (h) The documentation has been revised and clarified in places.
216    
217    9.  Improve the matching speed of capturing brackets.
218    
219    10. Changed the meaning of \X so that it now matches a Unicode extended
220        grapheme cluster.
221    
222    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
223        out POSIX threads when JIT support is configured.
224    
225    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
226    
227    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
228        structure could go wrong in environments where size_t is not the same size
229        as int.
230    
231    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
232        set.
233    
234    15. The EBCDIC support had decayed; later updates to the code had included
235        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
236        general tidy up of EBCDIC-related issues, and the documentation was also
237        not quite right. There is now a test that can be run on ASCII systems to
238        check some of the EBCDIC-related things (but is it not a full test).
239    
240    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
241        in a small tidy to the code.
242    
243    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
244    
245    18. If the --only-matching (-o) option in pcregrep is specified multiple
246        times, each one causes appropriate output. For example, -o1 -o2 outputs the
247        substrings matched by the 1st and 2nd capturing parentheses. A separating
248        string can be specified by --om-separator (default empty).
249    
250    19. Improving the first n character searches.
251    
252    20. Turn case lists for horizontal and vertical white space into macros so that
253        they are defined only once.
254    
255    21. This set of changes together give more compatible Unicode case-folding
256        behaviour for characters that have more than one other case when UCP
257        support is available.
258    
259        (a) The Unicode property table now has offsets into a new table of sets of
260            three or more characters that are case-equivalent. The MultiStage2.py
261            script that generates these tables (the pcre_ucd.c file) now scans
262            CaseFolding.txt instead of UnicodeData.txt for character case
263            information.
264    
265        (b) The code for adding characters or ranges of characters to a character
266            class has been abstracted into a generalized function that also handles
267            case-independence. In UTF-mode with UCP support, this uses the new data
268            to handle characters with more than one other case.
269    
270        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
271            whose other case is greater than 256 are now correctly matched
272            caselessly. Previously, the high codepoint matched the low one, but not
273            vice versa.
274    
275        (d) The processing of \h, \H, \v, and \ in character classes now makes use
276            of the new class addition function, using character lists defined as
277            macros alongside the case definitions of 20 above.
278    
279        (e) Caseless back references now work with characters that have more than
280            one other case.
281    
282        (f) General caseless matching of characters with more than one other case
283            is supported.
284    
285    22. Unicode character properties were updated from Unicode 6.2.0
286    
287    23. Improved CMake support under Windows. Patch by Daniel Richard G.
288    
289    24. Add support for 32-bit character strings, and UTF-32
290    
291    25. Major JIT compiler update (code refactoring and bugfixing).
292        Experimental Sparc 32 support is added.
293    
294    26. Applied a modified version of Daniel Richard G's patch to create
295        pcre.h.generic and config.h.generic by "make" instead of in the
296        PrepareRelease script.
297    
298    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
299        pcre_compile.c when checking for a zero character.
300    
301    28. Introducing a native interface for JIT. Through this interface, the compiled
302        machine code can be directly executed. The purpose of this interface is to
303        provide fast pattern matching, so several sanity checks are not performed.
304        However, feature tests are still performed. The new interface provides
305        1.4x speedup compared to the old one.
306    
307    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
308        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
309        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
310    
311    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
312        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
313        the "old" RFC 2279). Instead, it ended up passing a negative length to
314        pcre_exec().
315    
316    31. Add support for GCC's visibility feature to hide internal functions.
317    
318    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
319        "unknown -C option" after outputting 0 or 1.
320    
321    33. There is now support for generating a code coverage report for the test
322        suite in environments where gcc is the compiler and lcov is installed. This
323        is mainly for the benefit of the developers.
324    
325    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
326        unaddressable using valgrind annotations, allowing valgrind to detect
327        invalid memory accesses. This is mainly for the benefit of the developers.
328    
329    25. (*UTF) can now be used to start a pattern in any of the three libraries.
330    
331    26. Give configure error if --enable-cpp but no C++ compiler found.
332    
333    
334    Version 8.31 06-July-2012
335    -------------------------
336    
337  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
338    
339  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
340    
341  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
342      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
343      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
344    
345  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 348  Version 8.31
348      of more than one character:      of more than one character:
349    
350      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
351          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
352          references.          references.
353    
354      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
355          subject.          subject.
356    
357      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
358          characters at the end of the subject.          characters at the end of the subject.
359    
360      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 363  Version 8.31
363      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
364          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
365    
366  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
367      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
368      actually used to run the match.      actually used to run the match.
369    
370  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
371      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
372    
373  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 46  Version 8.31 Line 376  Version 8.31
376    
377  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
378      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
379    
380  11. Add PCRE_INFO_MAXLOOKBEHIND.  11. Add PCRE_INFO_MAXLOOKBEHIND.
381    
382  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
383      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
384      recursion). Instead of malloc and free for each heap frame each time a      recursion). Instead of malloc and free for each heap frame each time a
385      logical recursion happens, frames are retained on a chain and re-used where      logical recursion happens, frames are retained on a chain and re-used where
386      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
387    
388  13. (*COMMIT) is now correctly confined to within a recursive subpattern call.  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
389        call.
390    
391    14. As documented, (*COMMIT) is now confined to within a positive assertion.
392    
393    15. It is now possible to link pcretest with libedit as an alternative to
394        libreadline.
395    
396    16. (*COMMIT) control verb is now supported by the JIT compiler.
397    
398    17. The Unicode data tables have been updated to Unicode 6.1.0.
399    
400    18. Added --file-list option to pcregrep.
401    
402    19. Added binary file support to pcregrep, including the -a, --binary-files,
403        -I, and --text options.
404    
405    20. The madvise function is renamed for posix_madvise for QNX compatibility
406        reasons. Fixed by Giuseppe D'Angelo.
407    
408    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
409    
410    22. Changed the option for creating symbolic links for 16-bit man pages from
411        -s to -sf so that re-installing does not cause issues.
412    
413    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
414    
415    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
416        matches in certain environments (the workspace was not being correctly
417        retained). Also added to pcre_dfa_exec() a simple plausibility check on
418        some of the workspace data at the beginning of a restart.
419    
420    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
421        was not doing so when it should - probably a typo introduced by SVN 528
422        (change 8.10/14).
423    
424    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
425        \w+ when the character tables indicated that \x{c4} was a word character.
426        There were several related cases, all because the tests for doing a table
427        lookup were testing for characters less than 127 instead of 255.
428    
429    27. If a pattern contains capturing parentheses that are not used in a match,
430        their slots in the ovector are set to -1. For those that are higher than
431        any matched groups, this happens at the end of processing. In the case when
432        there were back references that the ovector was too small to contain
433        (causing temporary malloc'd memory to be used during matching), and the
434        highest capturing number was not used, memory off the end of the ovector
435        was incorrectly being set to -1. (It was using the size of the temporary
436        memory instead of the true size.)
437    
438    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
439        ovector size, it uses memory at the end of the block that it has got.
440    
441    29. Check for an overlong MARK name and give an error at compile time. The
442        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
443    
444    30. JIT compiler update.
445    
446    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
447        Rill for the patch.
448    
449    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
450    
451    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
452    
453    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
454        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
455        was enabled.
456    
457    35. Improve JIT code generation for greedy plus quantifier.
458    
459    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
460        1 to "aa" instead of to an empty string. The bug affected repeated groups
461        that could potentially match an empty string.
462    
463    37. Optimizing single character iterators in JIT.
464    
465    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
466        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
467        codepoints that are too big for the mode are faulted, and in a UTF mode,
468        disallowed codepoints are also faulted.
469    
470    39. If PCRE was compiled with UTF support, in three places in the DFA
471        matcher there was code that should only have been obeyed in UTF mode, but
472        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
473        processing when bytes with values greater than 127 were present. In 16-bit
474        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
475        both cases the values are those that cannot be the first data item in a UTF
476        character. The three items that might have provoked this were recursions,
477        possessively repeated groups, and atomic groups.
478    
479    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
480        and pcregrep, because some OS require shared objects to be explicitly
481        passed to ld, causing the link step to fail if they are not.
482    
483    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
484        mode, patterns that started with \h* or \R* might be incorrectly matched.
485    
486    
487  Version 8.30 04-February-2012  Version 8.30 04-February-2012
# Line 1248  Version 7.9 11-Apr-09 Line 1674  Version 7.9 11-Apr-09
1674  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1675      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1676      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1677      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1678        8.33.]
1679    
1680  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1681      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1491  Version 7.7 07-May-08 Line 1918  Version 7.7 07-May-08
1918      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1919      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1920      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1921      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
1922      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1923      was subsequently set up correctly.)      was subsequently set up correctly.)
1924    

Legend:
Removed from v.934  
changed lines
  Added in v.1334

  ViewVC Help
Powered by ViewVC 1.1.5