Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOC: Fix a typo in the 'Standalone Usage' section. #852

Merged
merged 1 commit into from
Oct 23, 2022
Merged

DOC: Fix a typo in the 'Standalone Usage' section. #852

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/html/math_toolkit/standalone.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@
Note that once the library is in standalone mode, you must have a conforming
C++11 compiler as no allowances will be made for possible compiler defects
which would otherwise be detected by Boost.Config. In addition, if you use
a section of the library which makes (possibly optionsal) use of features from
a section of the library which makes (possibly optional) use of features from
later C++ standards, then support for that later standard version becomes pretty
much mandatory. In other words, if you hit issues, try upping your compiler's
conformance level to C++17 if you can.
Expand Down
2 changes: 1 addition & 1 deletion doc/overview/standalone.qbk
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ In order to do this you must either:
* Define `BOOST_MATH_STANDALONE` on the compiler command line. This will force the library into standalone mode even when other Boost headers are present.

Note that once the library is in standalone mode, you must have a conforming C++11 compiler as no allowances will be made for possible compiler defects
which would otherwise be detected by Boost.Config. In addition, if you use a section of the library which makes (possibly optionsal) use of features from
which would otherwise be detected by Boost.Config. In addition, if you use a section of the library which makes (possibly optional) use of features from
later C++ standards, then support for that later standard version becomes pretty much mandatory. In other words, if you hit issues, try upping your compiler's
conformance level to C++17 if you can.

Expand Down