| /dports/accessibility/wl-gammarelay-rs/wl-gammarelay-rs-0.2.1/cargo-crates/wayland-protocols-0.30.0-alpha5/ |
| H A D | CHANGELOG.md | 10 - `wlr-output-management-unstable-v1` now marks `finished` event as destructor.
11 - `wlr-foreign-toplevel-management-unstable-v1` now marks `finished` event as destructor.
|
| /dports/archivers/7-zip/7-zip-21.07/CPP/7zip/ |
| H A D | warn_clang_mac.mak | 31 -Wno-suggest-destructor-override \
|
| /dports/archivers/brotli/brotli-1.0.9/python/ |
| H A D | _brotli.cc | 359 (destructor)brotli_Compressor_dealloc, /* tp_dealloc */
586 (destructor)brotli_Decompressor_dealloc, /* tp_dealloc */
|
| /dports/archivers/dpkg/dpkg-1.19.7/man/po/ |
| H A D | de.po | 17004 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | dpkg-man.pot | 13637 "instance of this case is a virtual destructor which under diamond "
|
| H A D | es.po | 17941 "case is a virtual destructor which under diamond inheritance needs a non-"
17953 "ejemplo común de este caso es un destructor virtual, que bajo una herencia "
|
| H A D | fr.po | 17091 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | hu.po | 14295 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | it.po | 17136 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | ja.po | 17610 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | nl.po | 17207 "case is a virtual destructor which under diamond inheritance needs a non-"
17220 "virtuele destructor die onder een diamantovererving een niet-virtueel thunk-"
|
| H A D | pl.po | 17935 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | pt_BR.po | 14152 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | ru.po | 14601 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | sv.po | 17587 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| H A D | zh_CN.po | 14211 "case is a virtual destructor which under diamond inheritance needs a non-"
|
| /dports/archivers/draco/googletest/docs/ |
| H A D | advanced.md | 262 [constructor/destructor vs. `SetUp`/`TearDown`](faq.md#CtorVsSetUp)
266 called from a constructor or destructor does not terminate the current test, as
268 destructor early, possibly leaving your object in a partially-constructed or
|
| H A D | faq.md | 306 ## Should I use the constructor/destructor of the test fixture or SetUp()/TearDown()? {#CtorVsSetUp}
314 between using the test fixture constructor/destructor or `SetUp()/TearDown()`.
322 the subclass' destructor is guaranteed to call the base class' destructor
337 * In the body of a constructor (or destructor), it's not possible to use the
343 `TearDown()` as opposed to the destructor, as throwing in a destructor leads
352 googletest assertions in a destructor if your code could run on such a
391 ## My compiler complains that a constructor (or destructor) cannot return a value. What's going on?
402 content of your constructor/destructor to a private void member function, or
|
| H A D | gmock_cook_book.md | 474 destructor of `MockFoo` is not virtual. We would like to fix this, but it
2872 class is in generating its constructor and destructor, as they perform
2880 mock class' constructor and destructor out of the class body and into a `.cc`
2882 only needs to generate its constructor and destructor once, resulting in a much
2893 // Since we don't declare the constructor or the destructor,
2910 // The constructor and destructor are declared, but not defined, here.
2963 // In case that server's destructor will forget to delete foo,
3034 calls, so all we need to do is to mock the destructor of the mock function.
3036 This sounds simple, except for one problem: a destructor is a special function
3046 destructor, like this:
[all …]
|
| H A D | gmock_faq.md | 140 destructor?
142 Whenever you derive from a base class, make sure its destructor is virtual.
|
| H A D | gmock_for_dummies.md | 118 (Note that the destructor of `Turtle` **must** be virtual, as is the case for
119 **all** classes you intend to inherit from - otherwise the destructor of the
593 relying on the constructor and destructor of this object to do the actual work,
|
| H A D | primer.md | 220 4. If necessary, write a destructor or `TearDown()` function to release any
222 constructor/destructor and when you should use `SetUp()/TearDown()`, read
291 each test, other than what's already done by the destructor.
417 // If the constructor and destructor are not enough for setting up
427 // before the destructor).
|
| /dports/archivers/draco/googletest/docs/reference/ |
| H A D | mocking.md | 464 `NiceMock<T>` might not work correctly if the destructor of `T` is not virtual.
522 `StrictMock<T>` might not work correctly if the destructor of `T` is not
|
| H A D | testing.md | 528 its constructor starts to the moment its destructor finishes) are output in XML
|
| /dports/archivers/lazperf/laz-perf-2.0.0/cpp/test/gtest/gtest-1.10.0/docs/ |
| H A D | advanced.md | 524 [constructor/destructor vs. `SetUp`/`TearDown`](faq.md#CtorVsSetUp)
527 called from a constructor or destructor does not does not terminate the current
529 destructor early, possibly leaving your object in a partially-constructed or
|