2001-04-09 11:17:40 +00:00
|
|
|
<html>
|
|
|
|
|
|
|
|
|
|
<head>
|
|
|
|
|
<meta http-equiv="Content-Type"
|
|
|
|
|
content="text/html; charset=iso-8859-1">
|
|
|
|
|
<meta name="keywords"
|
|
|
|
|
content="regex++, regular expressions, regular expression library, C++">
|
|
|
|
|
<meta name="Template"
|
|
|
|
|
content="C:\PROGRAM FILES\MICROSOFT OFFICE\OFFICE\html.dot">
|
|
|
|
|
<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
|
|
|
|
|
<title>regex++, Introduction</title>
|
|
|
|
|
</head>
|
|
|
|
|
|
|
|
|
|
<body bgcolor="#FFFFFF" link="#0000FF" vlink="#800080">
|
|
|
|
|
|
|
|
|
|
<p> </p>
|
|
|
|
|
|
|
|
|
|
<table border="0" cellpadding="7" cellspacing="0" width="624">
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top" width="50%"><h3><img
|
|
|
|
|
src="../../c++boost.gif" alt="C++ Boost" width="276"
|
|
|
|
|
height="86"></h3>
|
|
|
|
|
</td>
|
|
|
|
|
<td valign="top" width="50%"><h3 align="center">Regex++,
|
|
|
|
|
Introduction.</h3>
|
|
|
|
|
<p><i>(version 3.04, 18 April 2000)</i> </p>
|
|
|
|
|
<pre><i>Copyright (c) 1998-2000
|
2000-09-26 11:48:28 +00:00
|
|
|
Dr John Maddock
|
|
|
|
|
|
|
|
|
|
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.
|
2001-04-09 11:17:40 +00:00
|
|
|
It is provided "as is" without express or implied warranty.</i></pre>
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
<hr>
|
|
|
|
|
|
|
|
|
|
<h3><a name="intro"><i></i></a><i>Introduction</i></h3>
|
|
|
|
|
|
|
|
|
|
<p>Regular expressions are a form of pattern-matching that are
|
|
|
|
|
often used in text processing; many users will be familiar with
|
|
|
|
|
the Unix utilities <i>grep</i>, <i>sed</i> and <i>awk</i>, and
|
|
|
|
|
the programming language <i>perl</i>, each of which make
|
|
|
|
|
extensive use of regular expressions. Traditionally C++ users
|
|
|
|
|
have been limited to the POSIX C API's for manipulating regular
|
|
|
|
|
expressions, and while regex++ does provide these API's, they do
|
|
|
|
|
not represent the best way to use the library. For example regex++
|
|
|
|
|
can cope with wide character strings, or search and replace
|
|
|
|
|
operations (in a manner analogous to either sed or perl),
|
|
|
|
|
something that traditional C libraries can not do.</p>
|
|
|
|
|
|
|
|
|
|
<p>The class <a href="template_class_ref.htm#reg_expression">boost::reg_expression</a>
|
|
|
|
|
is the key class in this library; it represents a "machine
|
|
|
|
|
readable" regular expression, and is very closely modelled
|
|
|
|
|
on std::basic_string, think of it as a string plus the actual
|
|
|
|
|
state-machine required by the regular expression algorithms. Like
|
|
|
|
|
std::basic_string there are two typedefs that are almost always
|
|
|
|
|
the means by which this class is referenced:</p>
|
|
|
|
|
|
|
|
|
|
<pre><b>namespace </b>boost{
|
|
|
|
|
|
|
|
|
|
<b>template</b> <<b>class</b> charT,
|
|
|
|
|
<b> class</b> traits = regex_traits<charT>,
|
|
|
|
|
<b>class</b> Allocator = std::allocator<charT> >
|
|
|
|
|
<b>class</b> reg_expression;
|
|
|
|
|
|
|
|
|
|
<b>typedef</b> reg_expression<<b>char</b>> regex;
|
|
|
|
|
<b>typedef</b> reg_expression<<b>wchar_t></b> wregex;
|
|
|
|
|
|
|
|
|
|
}</pre>
|
|
|
|
|
|
|
|
|
|
<p>To see how this library can be used, imagine that we are
|
|
|
|
|
writing a credit card processing application. Credit card numbers
|
|
|
|
|
generally come as a string of 16-digits, separated into groups of
|
|
|
|
|
4-digits, and separated by either a space or a hyphen. Before
|
|
|
|
|
storing a credit card number in a database (not necessarily
|
|
|
|
|
something your customers will appreciate!), we may want to verify
|
|
|
|
|
that the number is in the correct format. To match any digit we
|
|
|
|
|
could use the regular expression [0-9], however ranges of
|
|
|
|
|
characters like this are actually locale dependent. Instead we
|
|
|
|
|
should use the POSIX standard form [[:digit:]], or the regex++
|
|
|
|
|
and perl shorthand for this \d (note that many older libraries
|
|
|
|
|
tended to be hard-coded to the C-locale, consequently this was
|
|
|
|
|
not an issue for them). That leaves us with the following regular
|
|
|
|
|
expression to validate credit card number formats:</p>
|
|
|
|
|
|
|
|
|
|
<p>(\d{4}[- ]){3}\d</p>
|
|
|
|
|
|
|
|
|
|
<p>Here the parenthesis act to group (and mark for future
|
|
|
|
|
reference) sub-expressions, and the {4} means "repeat
|
|
|
|
|
exactly 4 times". This is an example of the extended regular
|
|
|
|
|
expression syntax used by perl, awk and egrep. Regex++ also
|
|
|
|
|
supports the older "basic" syntax used by sed and grep,
|
|
|
|
|
but this is generally less useful, unless you already have some
|
|
|
|
|
basic regular expressions that you need to reuse.</p>
|
|
|
|
|
|
|
|
|
|
<p>Now lets take that expression and place it in some C++ code to
|
|
|
|
|
validate the format of a credit card number:</p>
|
|
|
|
|
|
|
|
|
|
<pre><b>bool</b> validate_card_format(<b>const</b> std::string s)
|
2000-09-26 11:48:28 +00:00
|
|
|
{
|
2001-04-09 11:17:40 +00:00
|
|
|
<b>static</b> <b>const</b> <a
|
|
|
|
|
href="template_class_ref.htm#reg_expression">boost::regex</a> e("(\\d{4}[- ]){3}\\d{4}");
|
|
|
|
|
<b>return</b> <a href="template_class_ref.htm#query_match">regex_match</a>(s, e);
|
|
|
|
|
}</pre>
|
|
|
|
|
|
|
|
|
|
<p>Note how we had to add some extra escapes to the expression:
|
|
|
|
|
remember that the escape is seen once by the C++ compiler, before
|
|
|
|
|
it gets to be seen by the regular expression engine, consequently
|
|
|
|
|
escapes in regular expressions have to be doubled up when
|
|
|
|
|
embedding them in C/C++ code.</p>
|
|
|
|
|
|
|
|
|
|
<p>Those of you who are familiar with credit card processing,
|
|
|
|
|
will have realised that while the format used above is suitable
|
|
|
|
|
for human readable card numbers, it does not represent the format
|
|
|
|
|
required by online credit card systems; these require the number
|
|
|
|
|
as a string of 16 (or possibly 15) digits, without any
|
|
|
|
|
intervening spaces. What we need is a means to convert easily
|
|
|
|
|
between the two formats, and this is where search and replace
|
|
|
|
|
comes in. Those who are familiar with the utilities <i>sed</i>
|
|
|
|
|
and <i>perl</i> will already be ahead here; we need two strings -
|
|
|
|
|
one a regular expression - the other a "<a
|
|
|
|
|
href="format_string.htm">format string</a>" that provides a
|
|
|
|
|
description of the text to replace the match with. In regex++
|
|
|
|
|
this search and replace operation is performed with the algorithm
|
|
|
|
|
regex_merge, for our credit card example we can write two
|
|
|
|
|
algorithms like this to provide the format conversions:</p>
|
|
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
<i>// match any format with the regular expression:
|
|
|
|
|
</i><b>const</b> boost::regex e("\\A(\\d{3,4})[- ]?(\\d{4})[- ]?(\\d{4})[- ]?(\\d{4})\\z");
|
|
|
|
|
<b>const</b> std::string machine_format("\\1\\2\\3\\4");
|
|
|
|
|
<b>const</b> std::string human_format("\\1-\\2-\\3-\\4");
|
|
|
|
|
|
|
|
|
|
std::string machine_readable_card_number(<b>const</b> std::string s)
|
2000-09-26 11:48:28 +00:00
|
|
|
{
|
2001-04-09 11:17:40 +00:00
|
|
|
<b>return</b> <a href="template_class_ref.htm#reg_merge">regex_merge</a>(s, e, machine_format, boost::match_default | boost::format_sed);
|
2000-09-26 11:48:28 +00:00
|
|
|
}
|
|
|
|
|
|
2001-04-09 11:17:40 +00:00
|
|
|
std::string human_readable_card_number(<b>const</b> std::string s)
|
2000-09-26 11:48:28 +00:00
|
|
|
{
|
2001-04-09 11:17:40 +00:00
|
|
|
<b>return</b> <a href="template_class_ref.htm#reg_merge">regex_merge</a>(s, e, human_format, boost::match_default | boost::format_sed);
|
|
|
|
|
}</pre>
|
|
|
|
|
|
|
|
|
|
<p>Here we've used marked sub-expressions in the regular
|
|
|
|
|
expression to split out the four parts of the card number as
|
|
|
|
|
separate fields, the format string then uses the sed-like syntax
|
|
|
|
|
to replace the matched text with the reformatted version.</p>
|
|
|
|
|
|
|
|
|
|
<p>In the examples above, we haven't directly manipulated the
|
|
|
|
|
results of a regular expression match, however in general the
|
|
|
|
|
result of a match contains a number of sub-expression matches in
|
|
|
|
|
addition to the overall match. When the library needs to report a
|
|
|
|
|
regular expression match it does so using an instance of the
|
|
|
|
|
class <a href="template_class_ref.htm#reg_match">match_results</a>,
|
|
|
|
|
as before there are typedefs of this class for the two most
|
|
|
|
|
common cases: </p>
|
|
|
|
|
|
|
|
|
|
<pre><b>namespace </b>boost{
|
|
|
|
|
<b>typedef</b> match_results<<b>const</b> <b>char</b>*> cmatch;
|
|
|
|
|
<b>typedef</b> match_results<<b>const</b> <b>wchar_t</b>*> wcmatch;
|
|
|
|
|
}</pre>
|
|
|
|
|
|
|
|
|
|
<p>The algorithms <a href="template_class_ref.htm#reg_search">regex_search</a>
|
|
|
|
|
and <a href="template_class_ref.htm#reg_grep">regex_grep</a> (i.e.
|
|
|
|
|
finding all matches in a string) make use of match_results to
|
|
|
|
|
report what matched.</p>
|
|
|
|
|
|
|
|
|
|
<p>Note that these algorithms are not restricted to searching
|
|
|
|
|
regular C-strings, any bidirectional iterator type can be
|
|
|
|
|
searched, allowing for the possibility of seamlessly searching
|
|
|
|
|
almost any kind of data. </p>
|
|
|
|
|
|
|
|
|
|
<p>For search and replace operations in addition to the algorithm
|
|
|
|
|
<a href="template_class_ref.htm#reg_merge">regex_merge</a> that
|
|
|
|
|
we have already seen, the algorithm <a
|
|
|
|
|
href="template_class_ref.htm#reg_format">regex_format</a> takes
|
|
|
|
|
the result of a match and a format string, and produces a new
|
|
|
|
|
string by merging the two.</p>
|
|
|
|
|
|
|
|
|
|
<p>For those that dislike templates, there is a high level
|
|
|
|
|
wrapper class RegEx that is an encapsulation of the lower level
|
|
|
|
|
template code - it provides a simplified interface for those that
|
|
|
|
|
don't need the full power of the library, and supports only
|
|
|
|
|
narrow characters, and the "extended" regular
|
|
|
|
|
expression syntax. </p>
|
|
|
|
|
|
|
|
|
|
<p>The <a href="posix_ref.htm#posix">POSIX API</a> functions:
|
|
|
|
|
regcomp, regexec, regfree and regerror, are available in both
|
|
|
|
|
narrow character and Unicode versions, and are provided for those
|
|
|
|
|
who need compatibility with these API's. </p>
|
|
|
|
|
|
|
|
|
|
<p>Finally, note that the library now has run-time <a
|
|
|
|
|
href="appendix.htm#localisation">localization</a> support, and
|
|
|
|
|
recognizes the full POSIX regular expression syntax - including
|
|
|
|
|
advanced features like multi-character collating elements and
|
|
|
|
|
equivalence classes - as well as providing compatibility with
|
|
|
|
|
other regular expression libraries including GNU and BSD4 regex
|
|
|
|
|
packages, and to a more limited extent perl 5. </p>
|
|
|
|
|
|
|
|
|
|
<h3><a name="Installation"><i></i></a><i>Installation and
|
|
|
|
|
Configuration Options</i> </h3>
|
|
|
|
|
|
|
|
|
|
<p><em>[ </em><strong><i>Important</i></strong><em>: If you are
|
|
|
|
|
upgrading from the 2.x version of this library then you will find
|
|
|
|
|
a number of changes to the documented header names and library
|
|
|
|
|
interfaces, existing code should still compile unchanged however
|
|
|
|
|
- see </em><a href="appendix.htm#upgrade"><font color="#0000FF"><em>Note
|
|
|
|
|
for Upgraders</em></font></a><em>. ]</em></p>
|
|
|
|
|
|
|
|
|
|
<p>When you extract the library from its zip file, you must
|
|
|
|
|
preserve its internal directory structure (for example by using
|
|
|
|
|
the -d option when extracting). If you didn't do that when
|
|
|
|
|
extracting, then you'd better stop reading this, delete the files
|
|
|
|
|
you just extracted, and try again! </p>
|
|
|
|
|
|
|
|
|
|
<p>Currently the library will automatically detect and configure
|
|
|
|
|
itself for Borland, Microsoft and gcc compilers only. The library
|
|
|
|
|
will also detect the HP, SGI, Rogue Wave, or Microsoft STL
|
|
|
|
|
implementations. If the STL type is detected, then the library
|
|
|
|
|
will attempt to extract suitable compiler configuration options
|
|
|
|
|
from the STL used. Otherwise the library will assume that the
|
|
|
|
|
compiler is fully compliant with the C++ standard: unless various
|
|
|
|
|
options are defined to depreciate features not implemented by
|
2001-04-12 11:14:59 +00:00
|
|
|
your compiler. These options are documented in <boost/regex/detail/regex_options.hpp>,
|
2001-04-09 11:17:40 +00:00
|
|
|
if you want to add permanent configuration options add them to
|
2001-04-12 11:14:59 +00:00
|
|
|
<boost/regex/detail/regex_options.hpp> which is provided for
|
2001-04-09 11:17:40 +00:00
|
|
|
this purpose - this will allow you to keep your configuration
|
2001-04-12 11:14:59 +00:00
|
|
|
options between library versions by retaining <boost/regex/detail/regex_options.hpp>.
|
2001-04-09 11:17:40 +00:00
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>The library will encase all code inside namespace boost. </p>
|
|
|
|
|
|
|
|
|
|
<p>Unlike some other template libraries, this library consists of
|
|
|
|
|
a mixture of template code (in the headers) and static code and
|
|
|
|
|
data (in cpp files). Consequently it is necessary to build the
|
|
|
|
|
library's support code into a library or archive file before you
|
|
|
|
|
can use it, instructions for specific platforms are as follows: </p>
|
|
|
|
|
|
|
|
|
|
<p><b>Borland C++ Builder:</b> </p>
|
|
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
<li>Open up a console window and change to the
|
|
|
|
|
<boost>\libs\regex\lib directory. </li>
|
|
|
|
|
<li>Select the appropriate makefile (bcb4.mak for C++ Builder
|
|
|
|
|
4, bcb5.mak for C++ Builder 5, and bcc55.mak for the 5.5
|
|
|
|
|
command line tools). </li>
|
|
|
|
|
<li>Invoke the makefile (pass the full path to your version
|
|
|
|
|
of make if you have more than one version installed, the
|
|
|
|
|
makefile relies on the path to make to obtain your C++
|
|
|
|
|
Builder installation directory and tools) for example: </li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<pre>make -fbcb5.mak</pre>
|
|
|
|
|
|
|
|
|
|
<p>The build process will build a variety of .lib and .dll files
|
|
|
|
|
(the exact number depends upon the version of Borland's tools you
|
|
|
|
|
are using) the .lib and dll files will be in a sub-directory
|
|
|
|
|
called bcb4 or bcb5 depending upon the makefile used. To install
|
|
|
|
|
the libraries into your development system use:</p>
|
|
|
|
|
|
|
|
|
|
<p>make -fbcb5.mak install</p>
|
|
|
|
|
|
|
|
|
|
<p>library files will be copied to <BCROOT>/lib and the
|
|
|
|
|
dll's to <BCROOT>/bin, where <BCROOT> corresponds to
|
|
|
|
|
the install path of your Borland C++ tools. </p>
|
|
|
|
|
|
|
|
|
|
<p>You may also remove temporary files created during the build
|
|
|
|
|
process (excluding lib and dll files) by using:</p>
|
|
|
|
|
|
|
|
|
|
<p>make -fbcb5.mak clean</p>
|
|
|
|
|
|
|
|
|
|
<p>Finally when you use regex++ it is only necessary for you to
|
|
|
|
|
add the <boost> root director to your list of include
|
|
|
|
|
directories for that project. It is not necessary for you to
|
|
|
|
|
manually add a .lib file to the project; the headers will
|
|
|
|
|
automatically select the correct .lib file for your build mode
|
|
|
|
|
and tell the linker to include it. There is one caveat however:
|
|
|
|
|
the library can not tell the difference between VCL and non-VCL
|
|
|
|
|
enabled builds when building a GUI application from the command
|
|
|
|
|
line, if you build from the command line with the 5.5 command
|
|
|
|
|
line tools then you must define the pre-processor symbol _NO_VCL
|
|
|
|
|
in order to ensure that the correct link libraries are selected:
|
|
|
|
|
the C++ Builder IDE normally sets this automatically. Hint, users
|
|
|
|
|
of the 5.5 command line tools may want to add a -D_NO_VCL to bcc32.cfg
|
|
|
|
|
in order to set this option permanently. <br>
|
|
|
|
|
<br>
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p><b>Microsoft Visual C++ 6</b> </p>
|
|
|
|
|
|
|
|
|
|
<p>You need version 6 of MSVC to build this library. If you are
|
|
|
|
|
using VC5 then you may want to look at one of the previous
|
|
|
|
|
releases of this <a
|
|
|
|
|
href="http://ourworld.compuserve.com/homepages/john_maddock/regexpp.htm">library</a>
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>Open up a command prompt, which has the necessary MSVC
|
|
|
|
|
environment variables defined (for example by using the batch
|
|
|
|
|
file Vcvars32.bat installed by the Visual Studio installation),
|
|
|
|
|
and change to the <boost>\libs\regex\lib directory. </p>
|
|
|
|
|
|
|
|
|
|
<p>Select the correct makefile - vc6.mak for "vanilla"
|
|
|
|
|
Visual C++ 6 or vc6-stlport.mak if you are using STLPort.</p>
|
|
|
|
|
|
|
|
|
|
<p>Invoke the makefile like this:</p>
|
|
|
|
|
|
|
|
|
|
<p>nmake -fvc6.mak</p>
|
|
|
|
|
|
|
|
|
|
<p>You will now have a collection of lib and dll files in a
|
|
|
|
|
"vc6" subdirectory, to install these into your
|
|
|
|
|
development system use:</p>
|
|
|
|
|
|
|
|
|
|
<p>nmake -fvc6.mak install</p>
|
|
|
|
|
|
|
|
|
|
<p>The lib files will be copied to your <VC6>\lib directory
|
|
|
|
|
and the dll files to <VC6>\bin, where <VC6> is the
|
|
|
|
|
root of your Visual C++ 6 installation.</p>
|
|
|
|
|
|
|
|
|
|
<p>You can delete all the temporary files created during the
|
|
|
|
|
build (excluding lib and dll files) using:</p>
|
|
|
|
|
|
|
|
|
|
<p>nmake -fvc6.mak clean </p>
|
|
|
|
|
|
|
|
|
|
<p>Finally when you use regex++ it is only necessary for you to
|
|
|
|
|
add the <boost> root directory to your list of include
|
|
|
|
|
directories for that project. It is not necessary for you to
|
|
|
|
|
manually add a .lib file to the project; the headers will
|
|
|
|
|
automatically select the correct .lib file for your build mode
|
|
|
|
|
and tell the linker to include it. </p>
|
|
|
|
|
|
|
|
|
|
<p>Note that if you want to statically link to the regex library
|
|
|
|
|
when using the dynamic C++ runtime, define BOOST_RE_STATIC_LIB
|
|
|
|
|
when building your project (this only has an effect for release
|
|
|
|
|
builds). If you want to add the source directly to your project
|
|
|
|
|
then define BOOST_RE_NO_LIB to disable automatic library
|
|
|
|
|
selection.</p>
|
|
|
|
|
|
|
|
|
|
<p><strong><i>Important</i></strong><em>: there have been some
|
|
|
|
|
reports of compiler-optimisation bugs affecting this library, the
|
|
|
|
|
workaround is to build the library using /Oityb1 rather than /O2.
|
|
|
|
|
That is to use all optimisation settings except /Oa. This problem
|
|
|
|
|
is reported to affect some standard library code as well (in fact
|
|
|
|
|
I'm not sure if the problem is with the regex code or the
|
|
|
|
|
underlying standard library), so it's probably worthwhile
|
|
|
|
|
applying this workaround in normal practice in any case.</em></p>
|
|
|
|
|
|
|
|
|
|
<p>Note: if you have replaced the C++ standard library that comes
|
|
|
|
|
with VC6, then when you build the library you must ensure that
|
|
|
|
|
the environment variables "INCLUDE" and "LIB"
|
|
|
|
|
have been updated to reflect the include and library paths for
|
|
|
|
|
the new library - see vcvars32.bat (part of your Visual Studio
|
|
|
|
|
installation) for more details. Alternatively if STLPort is in c:/stlport
|
|
|
|
|
then you could use:</p>
|
|
|
|
|
|
|
|
|
|
<p>nmake INCLUDES="-Ic:/stlport/stlport" XLFLAGS="/LIBPATH:c:/stlport/lib"
|
|
|
|
|
-fvc6-stlport.mak</p>
|
|
|
|
|
|
|
|
|
|
<p>If you are building with the full STLPort v4, then use the vc6-stlport.mak
|
|
|
|
|
file provided (The full STLPort libraries appear not to support
|
|
|
|
|
single-thread static builds). <br>
|
|
|
|
|
<br>
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p><b>GCC(2.95)</b> </p>
|
|
|
|
|
|
|
|
|
|
<p>There is a conservative makefile for the g++ compiler. From
|
2001-04-10 11:44:47 +00:00
|
|
|
the command prompt change to the <boost>/libs/regex/build
|
2001-04-09 11:17:40 +00:00
|
|
|
directory and type: </p>
|
|
|
|
|
|
|
|
|
|
<p>make -fgcc.mak </p>
|
|
|
|
|
|
|
|
|
|
<p>At the end of the build process you should have a gcc sub-directory
|
|
|
|
|
containing release and debug versions of the library (libboost_regex.a
|
|
|
|
|
and libboost_regex_debug.a). When you build projects that use
|
|
|
|
|
regex++, you will need to add the boost install directory to your
|
2001-04-10 11:44:47 +00:00
|
|
|
list of include paths and add <boost>/libs/regex/build/gcc/libboost_regex.a
|
2001-04-09 11:17:40 +00:00
|
|
|
to your list of library files. </p>
|
|
|
|
|
|
|
|
|
|
<p>There is also a makefile to build the library as a shared
|
|
|
|
|
library:</p>
|
|
|
|
|
|
|
|
|
|
<p>make -fgcc-shared.mak</p>
|
|
|
|
|
|
|
|
|
|
<p>which will build libboost_regex.so and libboost_regex_debug.so.</p>
|
|
|
|
|
|
|
|
|
|
<p>Both of the these makefiles support the following environment
|
|
|
|
|
variables:</p>
|
|
|
|
|
|
|
|
|
|
<p>CXXFLAGS: extra compiler options - note that this applies to
|
|
|
|
|
both the debug and release builds.</p>
|
|
|
|
|
|
|
|
|
|
<p>INCLUDES: additional include directories.</p>
|
|
|
|
|
|
|
|
|
|
<p>LDFLAGS: additional linker options.</p>
|
|
|
|
|
|
|
|
|
|
<p>LIBS: additional library files.</p>
|
|
|
|
|
|
|
|
|
|
<p>For the more adventurous there is a configure script in
|
|
|
|
|
<boost>/libs/regex, this will enable things like
|
|
|
|
|
multithreading/wide character/nls support if they are not enabled
|
|
|
|
|
by default on your platform. When the configure script completes,
|
|
|
|
|
run one of the makefiles described above.</p>
|
|
|
|
|
|
|
|
|
|
<p><b>Other compilers:</b> </p>
|
|
|
|
|
|
|
|
|
|
<p>Run configure, this will set up the headers and generate
|
|
|
|
|
makefiles: from the command prompt change to the <boost>/libs/regex
|
|
|
|
|
directory and type: </p>
|
|
|
|
|
|
|
|
|
|
<pre><tt>./configure
|
|
|
|
|
make</tt></pre>
|
|
|
|
|
|
|
|
|
|
<p>Other make options include: </p>
|
|
|
|
|
|
|
|
|
|
<p>make jgrep: builds the jgrep demo. </p>
|
|
|
|
|
|
|
|
|
|
<p>make test: builds and runs the regression tests. </p>
|
|
|
|
|
|
|
|
|
|
<p>make timer: builds the timer demo program. </p>
|
|
|
|
|
|
|
|
|
|
<p>Note that the configure generated makefiles produce only a
|
|
|
|
|
static library, if you would prefer to build a shared library,
|
2001-04-10 11:44:47 +00:00
|
|
|
then there is a generic.mak makefile in the <boost>/libs/regex/build
|
2001-04-09 11:17:40 +00:00
|
|
|
directory. To use this you will need to set up a number of
|
|
|
|
|
environment variables first (see the makefile for more details).
|
|
|
|
|
Finally if you use one of the following compilers: Kai C++, SGI
|
|
|
|
|
Irix C++, Compaq true64 C++, or Como C++, then you should not
|
|
|
|
|
need to run the configure script to get the library to build,
|
|
|
|
|
however doing so may enable optional features (multithreading
|
|
|
|
|
support, and/or nls support).</p>
|
|
|
|
|
|
|
|
|
|
<p><b>Troubleshooting:</b> </p>
|
|
|
|
|
|
|
|
|
|
<p>If make fails after running configure, you may need to
|
|
|
|
|
manually disable some options: configure uses simple tests to
|
|
|
|
|
determine what features your compiler supports, it does not
|
|
|
|
|
stress the compiler's internals to any degree as the actual regex++
|
|
|
|
|
code can do. Other compiler features may be implemented (and
|
|
|
|
|
therefore detected by configure) but known to be buggy, again in
|
|
|
|
|
this case it may be necessary to disable the feature in order to
|
|
|
|
|
compile regex++ to stable code. The output file from configure is
|
2001-04-12 11:14:59 +00:00
|
|
|
<boost>/boost/regex/detail/regex_options.hpp, this file lists
|
2001-04-09 11:17:40 +00:00
|
|
|
all the macros that can be defined to configure regex++ along
|
|
|
|
|
with a description to illustrate their usage, experiment changing
|
|
|
|
|
options in regex_options.hpp one at a time until you achieve the
|
|
|
|
|
effect you require. If you mail me questions about configure
|
|
|
|
|
output, be sure to include both regex_options.hpp and config.log
|
|
|
|
|
with your message. </p>
|
|
|
|
|
|
|
|
|
|
<hr>
|
|
|
|
|
|
|
|
|
|
<p><i>Copyright </i><a href="mailto:John_Maddock@compuserve.com"><i>Dr
|
|
|
|
|
John Maddock</i></a><i> 1998-2001 all rights reserved.</i> </p>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
