mirror of
https://github.com/boostorg/regex.git
synced 2025-07-29 20:17:24 +02:00
Document new build changes + standalone mode.
This commit is contained in:
@ -17,6 +17,22 @@ or platform) then [@../../../config/index.html Boost.Config] has a configure scr
|
||||
|
||||
[endsect]
|
||||
|
||||
[section:standalone Use in Standalone Mode (without the rest of Boost)]
|
||||
|
||||
This library may now be used in "standalone" mode without the rest of the Boost C++ libraries,
|
||||
in order to do this you must either:
|
||||
|
||||
* Have a C++17 compiler that supports `__has_include`, in this case if `<boost/config.hpp>` is *not* present
|
||||
then the library will automoatically enter standalone mode. Or:
|
||||
* Define BOOST_REGEX_STANDALONE when building.
|
||||
|
||||
The main difference between the 2 modes, is that when Boost.Config is present the library will automatically
|
||||
configure itself around various compiler defects. In particular in order to use the library with exception support
|
||||
turned off, you will either need a copy of Boost.Config in your include path, or else manually define BOOST_NO_EXCEPTIONS
|
||||
when building.
|
||||
|
||||
[endsect]
|
||||
|
||||
[section:locale Locale and traits class selection]
|
||||
|
||||
The following macros (see [@../../../../boost/regex/user.hpp user.hpp]) control how Boost.Regex interacts with
|
||||
@ -31,43 +47,11 @@ the user's locale:
|
||||
|
||||
[endsect]
|
||||
|
||||
|
||||
[section:linkage Linkage Options]
|
||||
|
||||
[table
|
||||
[[macro][description]]
|
||||
[[BOOST_REGEX_DYN_LINK][For Microsoft and Borland C++ builds, this tells Boost.Regex that it should link to the dll build of the Boost.Regex. By default boost.regex will link to its static library build, even if the dynamic C runtime library is in use.]]
|
||||
[[BOOST_REGEX_NO_LIB][For Microsoft and Borland C++ builds, this tells Boost.Regex that it should not automatically select the library to link to.]]
|
||||
[[BOOST_REGEX_NO_FASTCALL][For Microsoft builds, this tells Boost.Regex to use the `__cdecl` calling convention rather than `__fastcall`. Useful if you want to use the same library from both managed and unmanaged code.]]
|
||||
]
|
||||
|
||||
[endsect]
|
||||
|
||||
[section:algorithm Algorithm Selection]
|
||||
|
||||
[table
|
||||
[[macro][description]]
|
||||
[[BOOST_REGEX_RECURSIVE][Tells Boost.Regex to use a stack-recursive matching algorithm. This is generally the fastest option (although there is very little in it), but can cause stack overflow in extreme cases, on Win32 this can be handled safely, but this is not the case on other platforms.]]
|
||||
[[BOOST_REGEX_NON_RECURSIVE][Tells Boost.Regex to use a non-stack recursive matching algorithm, this can be slightly slower than the alternative, but is always safe no matter how pathological the regular expression. This is the default on non-Win32 platforms.]]
|
||||
]
|
||||
|
||||
[endsect]
|
||||
|
||||
[section:tuning Algorithm Tuning]
|
||||
|
||||
The following option applies only if BOOST_REGEX_RECURSIVE is set.
|
||||
|
||||
[table
|
||||
[[macro][description]]
|
||||
[[BOOST_REGEX_HAS_MS_STACK_GUARD][Tells Boost.Regex that Microsoft style __try - __except blocks are supported, and can be used to safely trap stack overflow.]]
|
||||
]
|
||||
|
||||
|
||||
The following options apply only if BOOST_REGEX_NON_RECURSIVE is set.
|
||||
|
||||
[table
|
||||
[[macro][description]]
|
||||
[[BOOST_REGEX_BLOCKSIZE][In non-recursive mode, Boost.Regex uses largish blocks of memory to act as a stack for the state machine, the larger the block size then the fewer allocations that will take place. This defaults to 4096 bytes, which is large enough to match the vast majority of regular expressions without further allocations, however, you can choose smaller or larger values depending upon your platforms characteristics.]]
|
||||
[[BOOST_REGEX_BLOCKSIZE][Boost.Regex uses largish blocks of memory to act as a stack for the state machine, the larger the block size then the fewer allocations that will take place. This defaults to 4096 bytes, which is large enough to match the vast majority of regular expressions without further allocations, however, you can choose smaller or larger values depending upon your platforms characteristics.]]
|
||||
[[BOOST_REGEX_MAX_BLOCKS][Tells Boost.Regex how many blocks of size BOOST_REGEX_BLOCKSIZE it is permitted to use. If this value is exceeded then Boost.Regex will stop trying to find a match and throw a std::runtime_error. Defaults to 1024, don't forget to tweak this value if you alter BOOST_REGEX_BLOCKSIZE by much.]]
|
||||
[[BOOST_REGEX_MAX_CACHE_BLOCKS][Tells Boost.Regex how many memory blocks to store in
|
||||
it's internal cache - memory blocks are taken from this cache rather than by calling
|
||||
|
Reference in New Issue
Block a user