mirror of
https://github.com/boostorg/parser.git
synced 2026-01-19 04:22:13 +00:00
Update config.hpp
This commit is contained in:
@@ -16,19 +16,19 @@
|
||||
|
||||
/** Boost.Parser uses assertions (`BOOST_ASSERT()`) in several places to
|
||||
indicate that your use of the library has an error in it. All of those
|
||||
places could heve instead been ill-formed code, caught at compile time.
|
||||
places could have instead been ill-formed code, caught at compile time.
|
||||
It is far quicker and easier to determine exactly where in your code such
|
||||
an error is located if this is a runtime failure; you can just look at the
|
||||
stack in your favorite debugger. However, if you want to make thes kinds
|
||||
stack in your favorite debugger. However, if you want to make these kinds
|
||||
of errors always ill-formed code, define this macro. */
|
||||
# define BOOST_PARSER_NO_RUNTIME_ASSERTIONS
|
||||
|
||||
/** Asserts that the given condition is true. If
|
||||
`BOOST_PARSER_NO_RUNTIME_ASSERTIONS` macro is defined by the user,
|
||||
`BOOST_PARSER_ASSERT` expends to a compile-time `static_assert()`.
|
||||
`BOOST_PARSER_ASSERT` expands to a compile-time `static_assert()`.
|
||||
Otherwise, it expands to a run-time `BOOST_ASSERT()`. Note that defining
|
||||
`BOOST_DISABLE_ASSERTS` disables the use of C `assert`, even when
|
||||
`BOOST_ASSERT` is unavailble. */
|
||||
`BOOST_ASSERT` is unavailable. */
|
||||
# define BOOST_PARSER_ASSERT(condition)
|
||||
|
||||
/** Boost.Parser will automatically use concepts to constrain templates when
|
||||
|
||||
Reference in New Issue
Block a user