| commit | 4c39bc6e9ca37fd6c3ec22da0c9549da4861b81f | |
| author | Olly Betts <olly@survex.com> | |
| Tue, 30 Aug 2022 05:21:28 +0000 (30 17:21 +1200) | ||
| committer | Olly Betts <olly@survex.com> | |
| Tue, 30 Aug 2022 05:25:52 +0000 (30 17:25 +1200) | ||
| tree | a08e250e22363df33745df61029daa2762a58e73 | treesnapshot (tar.gz zip) |
| parent | e01cb446bf34b75f8a32d0cff47dc8c846fa6a8b | commitdiff |
Refactor to avoid warning with GCC 12.2
GCC 12.2 warns about use of an object after it has been destroyed.
I'm not entirely convinced the warning is valid, but it's easy to
refactor to avoid it without making the code worse.
(cherry picked from commit 92c670ddd980f899b24403fa99a04e76404cca60)
GCC 12.2 warns about use of an object after it has been destroyed.
I'm not entirely convinced the warning is valid, but it's easy to
refactor to avoid it without making the code worse.
(cherry picked from commit 92c670ddd980f899b24403fa99a04e76404cca60)
| xapian-core/backends/inmemory/inmemory_database.cc | diffblobblamehistory | |
| xapian-core/backends/inmemory/inmemory_database.h | diffblobblamehistory |