outman/googletest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

modify macOS name

Browse Source
This commit is contained in:
Jack Lau 2024-12-02 13:46:40 +08:00 committed by JackLau1222
parent 35d0c36560
commit fac82b687b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faq.md
View File

@ -325,7 +325,7 @@ You may still want to use `SetUp()/TearDown()` in the following cases:
enabled in the compiler. Therefore you should prefer `TearDown()` if you enabled in the compiler. Therefore you should prefer `TearDown()` if you
want to write portable tests that work with or without exceptions. want to write portable tests that work with or without exceptions.
* The GoogleTest team is considering making the assertion macros throw on * The GoogleTest team is considering making the assertion macros throw on
platforms where exceptions are enabled (e.g. Windows, Mac OS, and Linux platforms where exceptions are enabled (e.g. Windows, macOS, and Linux
client-side), which will eliminate the need for the user to propagate client-side), which will eliminate the need for the user to propagate
failures from a subroutine to its caller. Therefore, you shouldn't use failures from a subroutine to its caller. Therefore, you shouldn't use
GoogleTest assertions in a destructor if your code could run on such a GoogleTest assertions in a destructor if your code could run on such a