mirror of
https://github.com/boostorg/regex.git
synced 2025-07-02 15:20:58 +02:00
Update history and regenerate docs.
This commit is contained in:
@ -18,6 +18,7 @@ All issues including closed ones can be viewed [@https://github.com/boostorg/reg
|
||||
|
||||
* [*Breaking Change:] Change \B to be the opposite of \b as per Perl behaviour.
|
||||
* Change w32_regex_traits.hpp so that windows.h is no longer included.
|
||||
* Fxed fuzzing related issues [@https://github.com/boostorg/regex/issues/156 #151], [@https://github.com/boostorg/regex/issues/156 #152], [@https://github.com/boostorg/regex/issues/156 #153], [@https://github.com/boostorg/regex/issues/156 #156].
|
||||
|
||||
[h4 Boost.Regex-6.0.0 (Boost-1.77.0)]
|
||||
|
||||
|
@ -47,6 +47,12 @@
|
||||
<li class="listitem">
|
||||
Change w32_regex_traits.hpp so that windows.h is no longer included.
|
||||
</li>
|
||||
<li class="listitem">
|
||||
Fxed fuzzing related issues <a href="https://github.com/boostorg/regex/issues/156" target="_top">#151</a>,
|
||||
<a href="https://github.com/boostorg/regex/issues/156" target="_top">#152</a>,
|
||||
<a href="https://github.com/boostorg/regex/issues/156" target="_top">#153</a>,
|
||||
<a href="https://github.com/boostorg/regex/issues/156" target="_top">#156</a>.
|
||||
</li>
|
||||
</ul></div>
|
||||
<h5>
|
||||
<a name="boost_regex.background.history.h1"></a>
|
||||
|
@ -106,7 +106,8 @@
|
||||
</p>
|
||||
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
|
||||
BOOST_REGEX_STANDALONE when set then no other Boost libraries are targeted
|
||||
as dependencies, and Boost.Regex is placed in standalone mode.
|
||||
as dependencies, and Boost.Regex is placed in standalone mode. Invoke CMake
|
||||
with -DBOOST_REGEX_STANDALONE=on to enable standalone mode.
|
||||
</li></ul></div>
|
||||
<h5>
|
||||
<a name="boost_regex.install.h1"></a>
|
||||
|
@ -364,9 +364,14 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table></div>
|
||||
<p>
|
||||
Note that a back reference can also be a forward-reference to a sub-expression
|
||||
that has not yet been seen - this only really makes sense within a repeat,
|
||||
so for example <code class="computeroutput"><span class="special">(\</span><span class="number">2</span><span class="identifier">two</span><span class="special">|(</span><span class="identifier">one</span><span class="special">))+</span></code> will match "oneonetwo".
|
||||
</p>
|
||||
<p>
|
||||
Finally the \k escape can be used to refer to named subexpressions, for example
|
||||
<code class="literal">\k<two></code> will match whatever matched the subexpression
|
||||
<code class="literal">\k<two></code> will whatever matched the subexpression
|
||||
named "two".
|
||||
</p>
|
||||
<h5>
|
||||
|
@ -215,7 +215,7 @@
|
||||
</p>
|
||||
</div>
|
||||
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
|
||||
<td align="left"><p><small>Last revised: October 10, 2021 at 15:39:14 GMT</small></p></td>
|
||||
<td align="left"><p><small>Last revised: November 05, 2021 at 17:17:10 GMT</small></p></td>
|
||||
<td align="right"><div class="copyright-footer"></div></td>
|
||||
</tr></table>
|
||||
<hr>
|
||||
|
Reference in New Issue
Block a user