/[pcre]/code/trunk/doc/html/pcrepattern.html

Diff of /code/trunk/doc/html/pcrepattern.html

Parent Directory | Revision Log | View Patch Patch

-revision 1403 by ph10,
Tue May 28 09:13:59 2013 UTC
+revision 1404 by ph10,
Tue Nov 19 15:36:57 2013 UTC
 Line 116 
 appearance causes an error.
  Unicode property support
  </b><br>
  <P>
- Another special sequence that may appear at the start of a pattern is
+ Another special sequence that may appear at the start of a pattern is (*UCP).
- <pre>
-   (*UCP)
- </pre>
  This has the same effect as setting the PCRE_UCP option: it causes sequences
  such as \d and \w to use Unicode properties to determine character types,
  instead of recognizing only characters with codes less than 128 via a lookup
  table.
  </P>
  <br><b>
+ Disabling auto-possessification
+ </b><br>
+ <P>
+ If a pattern starts with (*NO_AUTO_POSSESS), it has the same effect as setting
+ the PCRE_NO_AUTO_POSSESS option at compile time. This stops PCRE from making
+ quantifiers possessive when what follows cannot match the repeated item. For
+ example, by default a+b is treated as a++b. For more details, see the
+ <a href="pcreapi.html"><b>pcreapi</b></a>
+ documentation.
+ </P>
+ <br><b>
  Disabling start-up optimizations
  </b><br>
  <P>
  If a pattern starts with (*NO_START_OPT), it has the same effect as setting the
- PCRE_NO_START_OPTIMIZE option either at compile or matching time.
+ PCRE_NO_START_OPTIMIZE option either at compile or matching time. This disables
+ several optimizations for quickly reaching "no match" results. For more
+ details, see the
+ <a href="pcreapi.html"><b>pcreapi</b></a>
+ documentation.
  <a name="newlines"></a></P>
  <br><b>
  Newline conventions
-Line 193 
 pattern of the form
+Line 205 
 pattern of the form
    (*LIMIT_RECURSION=d)
  </pre>
  where d is any number of decimal digits. However, the value of the setting must
- be less than the value set by the caller of <b>pcre_exec()</b> for it to have
+ be less than the value set (or defaulted) by the caller of <b>pcre_exec()</b>
- any effect. In other words, the pattern writer can lower the limit set by the
+ for it to have any effect. In other words, the pattern writer can lower the
- programmer, but not raise it. If there is more than one setting of one of these
+ limits set by the programmer, but not raise them. If there is more than one
- limits, the lower value is used.
+ setting of one of these limits, the lower value is used.
  </P>
  <br><a name="SEC3" href="#TOC1">EBCDIC CHARACTER CODES</a><br>
  <P>
-Line 283 
 backslash. All other characters (in part
+Line 295 
 backslash. All other characters (in part
  greater than 127) are treated as literals.
  </P>
  <P>
- If a pattern is compiled with the PCRE_EXTENDED option, white space in the
+ If a pattern is compiled with the PCRE_EXTENDED option, most white space in the
- pattern (other than in a character class) and characters between a # outside
+ pattern (other than in a character class), and characters between a # outside a
- a character class and the next newline are ignored. An escaping backslash can
+ character class and the next newline, inclusive, are ignored. An escaping
- be used to include a white space or # character as part of the pattern.
+ backslash can be used to include a white space or # character as part of the
+ pattern.
  </P>
  <P>
  If you want to remove the special meaning from a sequence of characters, you
-Line 324 
 one of the following escape sequences th
+Line 337 
 one of the following escape sequences th
    \n        linefeed (hex 0A)
    \r        carriage return (hex 0D)
    \t        tab (hex 09)
+   \0dd      character with octal code 0dd
    \ddd      character with octal code ddd, or back reference
+   \o{ddd..} character with octal code ddd..
    \xhh      character with hex code hh
    \x{hhh..} character with hex code hhh.. (non-JavaScript mode)
    \uhhhh    character with hex code hhhh (JavaScript mode only)
-Line 347 
 the EBCDIC letters are disjoint, \cZ bec
+Line 362 
 the EBCDIC letters are disjoint, \cZ bec
  characters also generate different values.
  </P>
  <P>
- By default, after \x, from zero to two hexadecimal digits are read (letters
- can be in upper or lower case). Any number of hexadecimal digits may appear
- between \x{ and }, but the character code is constrained as follows:
- <pre>
--bit non-UTF mode    less than 0x100
--bit UTF-8 mode      less than 0x10ffff and a valid codepoint
--bit non-UTF mode   less than 0x10000
--bit UTF-16 mode    less than 0x10ffff and a valid codepoint
--bit non-UTF mode   less than 0x80000000
--bit UTF-32 mode    less than 0x10ffff and a valid codepoint
- </pre>
- Invalid Unicode codepoints are the range 0xd800 to 0xdfff (the so-called
- "surrogate" codepoints), and 0xffef.
- </P>
- <P>
- If characters other than hexadecimal digits appear between \x{ and }, or if
- there is no terminating }, this form of escape is not recognized. Instead, the
- initial \x will be interpreted as a basic hexadecimal escape, with no
- following digits, giving a character whose value is zero.
- </P>
- <P>
- If the PCRE_JAVASCRIPT_COMPAT option is set, the interpretation of \x is
- as just described only when it is followed by two hexadecimal digits.
- Otherwise, it matches a literal "x" character. In JavaScript mode, support for
- code points greater than 256 is provided by \u, which must be followed by
- four hexadecimal digits; otherwise it matches a literal "u" character.
- Character codes specified by \u in JavaScript mode are constrained in the same
- was as those specified by \x in non-JavaScript mode.
- </P>
- <P>
- Characters whose value is less than 256 can be defined by either of the two
- syntaxes for \x (or by \u in JavaScript mode). There is no difference in the
- way they are handled. For example, \xdc is exactly the same as \x{dc} (or
- \u00dc in JavaScript mode).
- </P>
- <P>
  After \0 up to two further octal digits are read. If there are fewer than two
  digits, just those that are present are used. Thus the sequence \0\x\07
  specifies two binary zeros followed by a BEL character (code value 7). Make
-Line 390 
 sure you supply two digits after the ini
+Line 369 
 sure you supply two digits after the ini
  follows is itself an octal digit.
  </P>
  <P>
- The handling of a backslash followed by a digit other than 0 is complicated.
+ The escape \o must be followed by a sequence of octal digits, enclosed in
- Outside a character class, PCRE reads it and any following digits as a decimal
+ braces. An error occurs if this is not the case. This escape is a recent
- number. If the number is less than 10, or if there have been at least that many
+ addition to Perl; it provides way of specifying character code points as octal
+ numbers greater than 0777, and it also allows octal numbers and back references
+ to be unambiguously specified.
+ </P>
+ <P>
+ For greater clarity and unambiguity, it is best to avoid following \ by a
+ digit greater than zero. Instead, use \o{} or \x{} to specify character
+ numbers, and \g{} to specify back references. The following paragraphs
+ describe the old, ambiguous syntax.
+ </P>
+ <P>
+ The handling of a backslash followed by a digit other than 0 is complicated,
+ and Perl has changed in recent releases, causing PCRE also to change. Outside a
+ character class, PCRE reads the digit and any following digits as a decimal
+ number. If the number is less than 8, or if there have been at least that many
  previous capturing left parentheses in the expression, the entire sequence is
  taken as a <i>back reference</i>. A description of how this works is given
  <a href="#backreferences">later,</a>
-Line 400 
 following the discussion of
+Line 393 
 following the discussion of
  <a href="#subpattern">parenthesized subpatterns.</a>
  </P>
  <P>
- Inside a character class, or if the decimal number is greater than 9 and there
+ Inside a character class, or if the decimal number following \ is greater than
- have not been that many capturing subpatterns, PCRE re-reads up to three octal
+and there have not been that many capturing subpatterns, PCRE handles \8 and
- digits following the backslash, and uses them to generate a data character. Any
+ \9 as the literal characters "8" and "9", and otherwise re-reads up to three
- subsequent digits stand for themselves. The value of the character is
+ octal digits following the backslash, using them to generate a data character.
- constrained in the same way as characters specified in hexadecimal.
+ Any subsequent digits stand for themselves. For example:
- For example:
  <pre>
    \040   is another way of writing an ASCII space
    \40    is the same, provided there are fewer than 40 previous capturing subpatterns
-Line 415 
 For example:
+Line 407 
 For example:
    \0113  is a tab followed by the character "3"
    \113   might be a back reference, otherwise the character with octal code 113
    \377   might be a back reference, otherwise the value 255 (decimal)
-   \81    is either a back reference, or a binary zero followed by the two characters "8" and "1"
+   \81    is either a back reference, or the two characters "8" and "1"
+ </pre>
+ Note that octal values of 100 or greater that are specified using this syntax
+ must not be introduced by a leading zero, because no more than three octal
+ digits are ever read.
+ </P>
+ <P>
+ By default, after \x that is not followed by {, from zero to two hexadecimal
+ digits are read (letters can be in upper or lower case). Any number of
+ hexadecimal digits may appear between \x{ and }. If a character other than
+ a hexadecimal digit appears between \x{ and }, or if there is no terminating
+ }, an error occurs.
+ </P>
+ <P>
+ If the PCRE_JAVASCRIPT_COMPAT option is set, the interpretation of \x is
+ as just described only when it is followed by two hexadecimal digits.
+ Otherwise, it matches a literal "x" character. In JavaScript mode, support for
+ code points greater than 256 is provided by \u, which must be followed by
+ four hexadecimal digits; otherwise it matches a literal "u" character.
+ </P>
+ <P>
+ Characters whose value is less than 256 can be defined by either of the two
+ syntaxes for \x (or by \u in JavaScript mode). There is no difference in the
+ way they are handled. For example, \xdc is exactly the same as \x{dc} (or
+ \u00dc in JavaScript mode).
+ </P>
+ <br><b>
+ Constraints on character values
+ </b><br>
+ <P>
+ Characters that are specified using octal or hexadecimal numbers are
+ limited to certain values, as follows:
+ <pre>
+-bit non-UTF mode    less than 0x100
+-bit UTF-8 mode      less than 0x10ffff and a valid codepoint
+-bit non-UTF mode   less than 0x10000
+-bit UTF-16 mode    less than 0x10ffff and a valid codepoint
+-bit non-UTF mode   less than 0x100000000
+-bit UTF-32 mode    less than 0x10ffff and a valid codepoint
  </pre>
- Note that octal values of 100 or greater must not be introduced by a leading
+ Invalid Unicode codepoints are the range 0xd800 to 0xdfff (the so-called
- zero, because no more than three octal digits are ever read.
+ "surrogate" codepoints), and 0xffef.
  </P>
+ <br><b>
+ Escape sequences in character classes
+ </b><br>
  <P>
  All the sequences that define a single character value can be used both inside
  and outside character classes. In addition, inside a character class, \b is
-Line 498 
 matching point is at the end of the subj
+Line 531 
 matching point is at the end of the subj
  there is no character to match.
  </P>
  <P>
- For compatibility with Perl, \s does not match the VT character (code 11).
+ For compatibility with Perl, \s did not used to match the VT character (code
- This makes it different from the the POSIX "space" class. The \s characters
+), which made it different from the the POSIX "space" class. However, Perl
- are HT (9), LF (10), FF (12), CR (13), and space (32). If "use locale;" is
+ added VT at release 5.18, and PCRE followed suit at release 8.34. The default
- included in a Perl script, \s may match the VT character. In PCRE, it never
+ \s characters are now HT (9), LF (10), VT (11), FF (12), CR (13), and space
- does.
+ (32), which are defined as white space in the "C" locale. This list may vary if
+ locale-specific matching is taking place; in particular, in some locales the
+ "non-breaking space" character (\xA0) is recognized as white space.
  </P>
  <P>
  A "word" character is an underscore or any character that is a letter or digit.
-Line 513 
 place (see
+Line 548 
 place (see
  in the
  <a href="pcreapi.html"><b>pcreapi</b></a>
  page). For example, in a French locale such as "fr_FR" in Unix-like systems,
- or "french" in Windows, some character codes greater than 128 are used for
+ or "french" in Windows, some character codes greater than 127 are used for
  accented letters, and these are then matched by \w. The use of locales with
  Unicode is discouraged.
  </P>
  <P>
- By default, in a UTF mode, characters with values greater than 128 never match
+ By default, characters whose code points are greater than 127 never match \d,
- \d, \s, or \w, and always match \D, \S, and \W. These sequences retain
+ \s, or \w, and always match \D, \S, and \W, although this may vary for
- their original meanings from before UTF support was available, mainly for
+ characters in the range 128-255 when locale-specific matching is happening.
- efficiency reasons. However, if PCRE is compiled with Unicode property support,
+ These escape sequences retain their original meanings from before Unicode
- and the PCRE_UCP option is set, the behaviour is changed so that Unicode
+ support was available, mainly for efficiency reasons. If PCRE is compiled with
- properties are used to determine character types, as follows:
+ Unicode property support, and the PCRE_UCP option is set, the behaviour is
- <pre>
+ changed so that Unicode properties are used to determine character types, as
-   \d  any character that \p{Nd} matches (decimal digit)
+ follows:
-   \s  any character that \p{Z} matches, plus HT, LF, FF, CR
+ <pre>
-   \w  any character that \p{L} or \p{N} matches, plus underscore
+   \d  any character that matches \p{Nd} (decimal digit)
+   \s  any character that matches \p{Z} or \h or \v
+   \w  any character that matches \p{L} or \p{N}, plus underscore
  </pre>
  The upper case escapes match the inverse sets of characters. Note that \d
  matches only decimal digits, whereas \w matches any Unicode digit, as well as
-Line 538 
 is noticeably slower when PCRE_UCP is se
+Line 575 
 is noticeably slower when PCRE_UCP is se
  <P>
  The sequences \h, \H, \v, and \V are features that were added to Perl at
  release 5.10. In contrast to the other sequences, which match only ASCII
- characters by default, these always match certain high-valued codepoints,
+ characters by default, these always match certain high-valued code points,
  whether or not PCRE_UCP is set. The horizontal space characters are:
  <pre>
    U+0009     Horizontal tab (HT)
-Line 913 
 PCRE's additional properties
+Line 950 
 PCRE's additional properties
  <P>
  As well as the standard Unicode properties described above, PCRE supports four
  more that make it possible to convert traditional escape sequences such as \w
- and \s and POSIX character classes to use Unicode properties. PCRE uses these
+ and \s to use Unicode properties. PCRE uses these non-standard, non-Perl
- non-standard, non-Perl properties internally when PCRE_UCP is set. However,
+ properties internally when PCRE_UCP is set. However, they may also be used
- they may also be used explicitly. These properties are:
+ explicitly. These properties are:
  <pre>
    Xan   Any alphanumeric character
    Xps   Any POSIX space character
-Line 925 
 they may also be used explicitly. These
+Line 962 
 they may also be used explicitly. These
  Xan matches characters that have either the L (letter) or the N (number)
  property. Xps matches the characters tab, linefeed, vertical tab, form feed, or
  carriage return, and any other character that has the Z (separator) property.
- Xsp is the same as Xps, except that vertical tab is excluded. Xwd matches the
+ Xsp is the same as Xps; it used to exclude vertical tab, for Perl
- same characters as Xan, plus underscore.
+ compatibility, but Perl changed, and so PCRE followed at release 8.34. Xwd
+ matches the same characters as Xan, plus underscore.
  </P>
  <P>
  There is another non-standard property, Xuc, which matches any character that
-Line 1218 
 The minus (hyphen) character can be used
+Line 1256 
 The minus (hyphen) character can be used
  character class. For example, [d-m] matches any letter between d and m,
  inclusive. If a minus character is required in a class, it must be escaped with
  a backslash or appear in a position where it cannot be interpreted as
- indicating a range, typically as the first or last character in the class.
+ indicating a range, typically as the first or last character in the class, or
+ immediately after a range. For example, [b-d-z] matches letters in the range b
+ to d, a hyphen character, or z.
  </P>
  <P>
  It is not possible to have the literal character "]" as the end character of a
-Line 1230 
 followed by two other characters. The oc
+Line 1270 
 followed by two other characters. The oc
  "]" can also be used to end a range.
  </P>
  <P>
+ An error is generated if a POSIX character class (see below) or an escape
+ sequence other than one that defines a single character appears at a point
+ where a range ending character is expected. For example, [z-\xff] is valid,
+ but [A-\d] and [A-[:digit:]] are not.
+ </P>
+ <P>
  Ranges operate in the collating sequence of character values. They can also be
  used for characters specified numerically, for example [\000-\037]. Ranges
  can include any characters that are valid for the current mode.
-Line 1294 
 are:
+Line 1340 
 are:
    lower    lower case letters
    print    printing characters, including space
    punct    printing characters, excluding letters and digits and space
-   space    white space (not quite the same as \s)
+   space    white space (the same as \s from PCRE 8.34)
    upper    upper case letters
    word     "word" characters (same as \w)
    xdigit   hexadecimal digits
  </pre>
- The "space" characters are HT (9), LF (10), VT (11), FF (12), CR (13), and
+ The default "space" characters are HT (9), LF (10), VT (11), FF (12), CR (13),
- space (32). Notice that this list includes the VT character (code 11). This
+ and space (32). If locale-specific matching is taking place, there may be
- makes "space" different to \s, which does not include VT (for Perl
+ additional space characters. "Space" used to be different to \s, which did not
- compatibility).
+ include VT, for Perl compatibility. However, Perl changed at release 5.18, and
+ PCRE followed at release 8.34. "Space" and \s now match the same set of
+ characters.
  </P>
  <P>
  The name "word" is a Perl extension, and "blank" is a GNU extension from Perl
-Line 1316 
 syntax [.ch.] and [=ch=] where "ch" is a
+Line 1364 
 syntax [.ch.] and [=ch=] where "ch" is a
  supported, and an error is given if they are encountered.
  </P>
  <P>
- By default, in UTF modes, characters with values greater than 128 do not match
+ By default, characters with values greater than 128 do not match any of the
- any of the POSIX character classes. However, if the PCRE_UCP option is passed
+ POSIX character classes. However, if the PCRE_UCP option is passed to
- to <b>pcre_compile()</b>, some of the classes are changed so that Unicode
+ <b>pcre_compile()</b>, some of the classes are changed so that Unicode character
- character properties are used. This is achieved by replacing the POSIX classes
+ properties are used. This is achieved by replacing certain POSIX classes by
- by other sequences, as follows:
+ other sequences, as follows:
  <pre>
    [:alnum:]  becomes  \p{Xan}
    [:alpha:]  becomes  \p{L}
-Line 1331 
 by other sequences, as follows:
+Line 1379 
 by other sequences, as follows:
    [:upper:]  becomes  \p{Lu}
    [:word:]   becomes  \p{Xwd}
  </pre>
- Negated versions, such as [:^alpha:] use \P instead of \p. The other POSIX
+ Negated versions, such as [:^alpha:] use \P instead of \p. Three other POSIX
- classes are unchanged, and match only characters with code points less than
+ classes are handled specially in UCP mode:
-.
+ </P>
+ <P>
+ [:graph:]
+ This matches characters that have glyphs that mark the page when printed. In
+ Unicode property terms, it matches all characters with the L, M, N, P, S, or Cf
+ properties, except for:
+ <pre>
+   U+061C           Arabic Letter Mark
+   U+180E           Mongolian Vowel Separator
+   U+2066 - U+2069  Various "isolate"s
+ </PRE>
+ </P>
+ <P>
+ [:print:]
+ This matches the same characters as [:graph:] plus space characters that are
+ not controls, that is, characters with the Zs property.
+ </P>
+ <P>
+ [:punct:]
+ This matches all characters that have the Unicode P (punctuation) property,
+ plus those characters whose code points are less than 128 that have the S
+ (Symbol) property.
+ </P>
+ <P>
+ The other POSIX classes are unchanged, and match only characters with code
+ points less than 128.
  </P>
  <br><a name="SEC11" href="#TOC1">VERTICAL BAR</a><br>
  <P>
-Line 1535 
 and
+Line 1609 
 and
  can be made by name as well as by number.
  </P>
  <P>
- Names consist of up to 32 alphanumeric characters and underscores. Named
+ Names consist of up to 32 alphanumeric characters and underscores, but must
- capturing parentheses are still allocated numbers as well as names, exactly as
+ start with a non-digit. Named capturing parentheses are still allocated numbers
- if the names were not present. The PCRE API provides function calls for
+ as well as names, exactly as if the names were not present. The PCRE API
- extracting the name-to-number translation table from a compiled pattern. There
+ provides function calls for extracting the name-to-number translation table
- is also a convenience function for extracting a captured substring by name.
+ from a compiled pattern. There is also a convenience function for extracting a
+ captured substring by name.
  </P>
  <P>
  By default, a name must be unique within a pattern, but it is possible to relax
-Line 1568 
 matched. This saves searching to find wh
+Line 1643 
 matched. This saves searching to find wh
  </P>
  <P>
  If you make a back reference to a non-unique named subpattern from elsewhere in
- the pattern, the one that corresponds to the first occurrence of the name is
+ the pattern, the subpatterns to which the name refers are checked in the order
- used. In the absence of duplicate numbers (see the previous section) this is
+ in which they appear in the overall pattern. The first one that is set is used
- the one with the lowest number. If you use a named reference in a condition
+ for the reference. For example, this pattern matches both "foofoo" and
+ "barbar" but not "foobar" or "barfoo":
+ <pre>
+   (?:(?&#60;n&#62;foo)|(?&#60;n&#62;bar))\k&#60;n&#62;
+ </PRE>
+ </P>
+ <P>
+ If you make a subroutine call to a non-unique named subpattern, the one that
+ corresponds to the first occurrence of the name is used. In the absence of
+ duplicate numbers (see the previous section) this is the one with the lowest
+ number.
+ </P>
+ <P>
+ If you use a named reference in a condition
  test (see the
  <a href="#conditions">section about conditions</a>
  below), either to check whether a subpattern has matched, or to check for
-Line 1585 
 documentation.
+Line 1674 
 documentation.
  <b>Warning:</b> You cannot use different names to distinguish between two
  subpatterns with the same number because PCRE uses only the numbers when
  matching. For this reason, an error is given at compile time if different names
- are given to subpatterns with the same number. However, you can give the same
+ are given to subpatterns with the same number. However, you can always give the
- name to subpatterns with the same number, even when PCRE_DUPNAMES is not set.
+ same name to subpatterns with the same number, even when PCRE_DUPNAMES is not
+ set.
  </P>
  <br><a name="SEC16" href="#TOC1">REPETITION</a><br>
  <P>
-Line 2252 
 Checking for a used subpattern by name
+Line 2342 
 Checking for a used subpattern by name
  <P>
  Perl uses the syntax (?(&#60;name&#62;)...) or (?('name')...) to test for a used
  subpattern by name. For compatibility with earlier versions of PCRE, which had
- this facility before Perl, the syntax (?(name)...) is also recognized. However,
+ this facility before Perl, the syntax (?(name)...) is also recognized.
- there is a possible ambiguity with this syntax, because subpattern names may
- consist entirely of digits. PCRE looks first for a named subpattern; if it
- cannot find one and the name consists entirely of digits, PCRE looks for a
- subpattern of that number, which must be greater than zero. Using subpattern
- names that consist entirely of digits is not recommended.
  </P>
  <P>
  Rewriting the above example to use a named subpattern gives this:
-Line 2674 
 During matching, when PCRE reaches a cal
+Line 2759 
 During matching, when PCRE reaches a cal
  called. It is provided with the number of the callout, the position in the
  pattern, and, optionally, one item of data originally supplied by the caller of
  the matching function. The callout function may cause matching to proceed, to
- backtrack, or to fail altogether. A complete description of the interface to
+ backtrack, or to fail altogether.
- the callout function is given in the
+ </P>
+ <P>
+ By default, PCRE implements a number of optimizations at compile time and
+ matching time, and one side-effect is that sometimes callouts are skipped. If
+ you need all possible callouts to happen, you need to set options that disable
+ the relevant optimizations. More details, and a complete description of the
+ interface to the callout function, are given in the
  <a href="pcrecallout.html"><b>pcrecallout</b></a>
  documentation.
  <a name="backtrackcontrol"></a></P>
-Line 3026 
 example:
+Line 3117 
 example:
  <pre>
    ...(*COMMIT)(*PRUNE)...
  </pre>
- If there is a matching failure to the right, backtracking onto (*PRUNE) cases
+ If there is a matching failure to the right, backtracking onto (*PRUNE) causes
  it to be triggered, and its action is taken. There can never be a backtrack
  onto (*COMMIT).
  <a name="btrepeat"></a></P>
-Line 3109 
 Cambridge CB2 3QH, England.
+Line 3200 
 Cambridge CB2 3QH, England.
  </P>
  <br><a name="SEC29" href="#TOC1">REVISION</a><br>
  <P>
- Last updated: 26 April 2013
+ Last updated: 12 November 2013
  <br>
  Copyright &copy; 1997-2013 University of Cambridge.
  <br>

 Legend:



Removed from v.1403
 


changed lines


 
Added in v.1404
 Legend:



Removed from v.1403
 


changed lines


 
Added in v.1404
-Removed from v.1403
+Added in v.1404

	ViewVC Help
Powered by ViewVC 1.1.5