opentrack.git/tracker-pt/point_tracker.h, branch opentrack-2.3.12head tracking software for Windows and Linuxhttp://ananke.misaki.pl/cgit/opentrack.git/atom?h=opentrack-2.3.122019-02-21T18:17:21Ztracker/pt: don't `namespace pt_module' for core PT stuff2019-02-21T18:17:21ZStanislaw Haliksthalik@misaki.pl2019-02-21T18:11:19Zurn:sha1:ff38e35d832b7c7a3e189bee4a80271fd3a3c978modernize only2019-01-16T06:49:10ZStanislaw Haliksthalik@misaki.pl2019-01-14T15:21:56Zurn:sha1:42e6b27e1afda7fcd8beddd9676ba7edb6363a34
- replace `static constexpr inline' with `static constexpr'.
`inline' is implied.
- use braced initializer lists where applicable
- still missing `override' usages
cv/numeric: rename namespace2019-01-16T06:48:46ZStanislaw Haliksthalik@misaki.pl2019-01-07T10:06:14Zurn:sha1:b6b1f969bcf0fe0b3551f01b90d41fab99372a99tracker/pt: retire pose reuse2019-01-16T06:48:20ZStanislaw Haliksthalik@misaki.pl2019-01-06T11:48:53Zurn:sha1:9f365bc81f9d7a3bb0b31261776580b178e02ce2tracker/pt: set expected pose to identity reset_state()2019-01-16T06:48:20ZStanislaw Haliksthalik@misaki.pl2019-01-03T22:36:23Zurn:sha1:eb1ad39023671ec6980f8631179452423de15e90
Also there's this evil `static' but it probably resulted in having it
set to identity anyway.
tracker/pt: cleanup, declarations, lock scope2019-01-16T06:48:19ZStanislaw Haliksthalik@misaki.pl2018-12-29T15:49:56Zurn:sha1:a0bc55227ca1511a0c705e89c308ecbbdc7124c8silly busywork2018-10-05T14:35:44ZStanislaw Haliksthalik@misaki.pl2018-10-05T13:59:58Zurn:sha1:9cca4ffd9987352e43119d9c4dea0ce84c2c448fappease analyzer2018-07-13T14:20:30ZStanislaw Haliksthalik@misaki.pl2018-07-13T14:20:30Zurn:sha1:68f5f213bf0cbd0bd60a6849bf4379113ea06282cleanup only2018-07-09T03:35:08ZStanislaw Haliksthalik@misaki.pl2018-07-09T03:33:58Zurn:sha1:793cea587159a0ba01fec6af28e899697ef4da79clean up "static" and "constexpr" types2018-02-15T09:23:11ZStanislaw Haliksthalik@misaki.pl2018-02-15T08:06:13Zurn:sha1:0a92bc147f91f3ecacdf66d995f01f9577107a86
- use `static constexpr inline' to avoid requiring
explicit declarations in object code
- use `const Foo* const' to maybe put into readonly
binary segment (at least for ELF DSOs)
- `constexpr' in function scope has storage, avoid
`static'
- don't use `constexpr' where there's no advantage,
like arrays
We'd like to avoid overhead of atomic initialization
for each function call. No idea how `static constexpr'
requiring storage in the standard plays with atomic
initialization requirement. Hearsay points that
`constexpr' without `static' in block scope behaves
more to our liking. It's all hazy though.
I'm not 100% sure if `static inline constexpr' has any
storage. Hopefully none, like a #define, and stuff
bigger than registers gets coalesced within the same
module, with small stuff being immediates.