mirror of
https://github.com/boostorg/regex.git
synced 2025-07-14 12:56:36 +02:00
80 lines
4.1 KiB
HTML
80 lines
4.1 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|||
|
|
<html>
|
|||
|
|
<head>
|
|||
|
|
<title>Boost.Regex: Standards Conformance</title>
|
|||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
|||
|
|
<link rel="stylesheet" type="text/css" href="../../../boost.css">
|
|||
|
|
</head>
|
|||
|
|
<body>
|
|||
|
|
<P>
|
|||
|
|
<TABLE id="Table1" cellSpacing="1" cellPadding="1" width="100%" border="0">
|
|||
|
|
<TR>
|
|||
|
|
<td valign="top" width="300">
|
|||
|
|
<h3><a href="../../../index.htm"><img height="86" width="277" alt="C++ Boost" src="../../../c++boost.gif" border="0"></a></h3>
|
|||
|
|
</td>
|
|||
|
|
<TD width="353">
|
|||
|
|
<H1 align="center">Boost.Regex</H1>
|
|||
|
|
<H2 align="center">Standards Conformance</H2>
|
|||
|
|
</TD>
|
|||
|
|
<td width="50">
|
|||
|
|
<h3><a href="index.html"><img height="45" width="43" alt="Boost.Regex Index" src="uarrow.gif" border="0"></a></h3>
|
|||
|
|
</td>
|
|||
|
|
</TR>
|
|||
|
|
</TABLE>
|
|||
|
|
</P>
|
|||
|
|
<HR>
|
|||
|
|
<H3>C++</H3>
|
|||
|
|
<P>Boost.regex is intended to conform to the <A href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1429.htm">
|
|||
|
|
regular expression standardization proposal</A>, which will appear in a
|
|||
|
|
future C++ standard technical report (and hopefully in a future version of the
|
|||
|
|
standard). Currently there are some differences in how the regular
|
|||
|
|
expression traits classes are defined, these will be fixed in a future release.</P>
|
|||
|
|
<H3>ECMAScript / JavaScript</H3>
|
|||
|
|
<P>All of the ECMAScript regular expression syntax features are supported, except
|
|||
|
|
that:</P>
|
|||
|
|
<P>Negated class escapes (\S, \D and \W) are not permitted inside character class
|
|||
|
|
definitions ( [...] ).</P>
|
|||
|
|
<P>The escape sequence \u matches any upper case character (the same as
|
|||
|
|
[[:upper:]]) rather than a Unicode escape sequence; use \x{DDDD} for
|
|||
|
|
Unicode escape sequences.</P>
|
|||
|
|
<H3>Perl</H3>
|
|||
|
|
<P>Almost all Perl features are supported, except for:</P>
|
|||
|
|
<P>\N{name} Use [[:name:]] instead.</P>
|
|||
|
|
<P>\pP and \PP</P>
|
|||
|
|
<P>(?imsx-imsx)</P>
|
|||
|
|
<P>(?<=pattern)</P>
|
|||
|
|
<P>(?<!pattern)</P>
|
|||
|
|
<P>(?{code})</P>
|
|||
|
|
<P>(??{code})</P>
|
|||
|
|
<P>(?(condition)yes-pattern) and (?(condition)yes-pattern|no-pattern)</P>
|
|||
|
|
<P>These embarrassments / limitations will be removed in due course, mainly
|
|||
|
|
dependent upon user demand.</P>
|
|||
|
|
<H3>POSIX</H3>
|
|||
|
|
<P>All the POSIX basic and extended regular expression features are supported,
|
|||
|
|
except that:</P>
|
|||
|
|
<P>No character collating names are recognized except those specified in the POSIX
|
|||
|
|
standard for the C locale, unless they are explicitly registered with the
|
|||
|
|
traits class.</P>
|
|||
|
|
<P>Character equivalence classes ( [[=a=]] etc) are probably buggy except on
|
|||
|
|
Win32. Implementing this feature requires knowledge of the format of the
|
|||
|
|
string sort keys produced by the system; if you need this, and the default
|
|||
|
|
implementation doesn't work on your platform, then you will need to supply a
|
|||
|
|
custom traits class.</P>
|
|||
|
|
<HR>
|
|||
|
|
<p>Revised
|
|||
|
|
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
|
|||
|
|
17 May 2003
|
|||
|
|
<!--webbot bot="Timestamp" endspan i-checksum="39359" -->
|
|||
|
|
</p>
|
|||
|
|
<P><I><EFBFBD> Copyright <a href="mailto:jm@regex.fsnet.co.uk">John Maddock</a> 1998-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%Y" startspan --> 2003<!--webbot bot="Timestamp" endspan i-checksum="39359" --></I></P>
|
|||
|
|
<P align="left"><I>Permission to use, copy, modify, distribute and sell this software
|
|||
|
|
and its documentation for any purpose is hereby granted without fee, provided
|
|||
|
|
that the above copyright notice appear in all copies and that both that
|
|||
|
|
copyright notice and this permission notice appear in supporting documentation.
|
|||
|
|
Dr John Maddock makes no representations about the suitability of this software
|
|||
|
|
for any purpose. It is provided "as is" without express or implied warranty.</I></P>
|
|||
|
|
</body>
|
|||
|
|
</html>
|
|||
|
|
|
|||
|
|
|