Age | Commit message (Collapse) | Author |
|
- 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.
|
|
cf. #746
|
|
Now i18n regen won't make a mess.
|
|
|
|
Adjust usages.
|
|
|
|
It's a contract for plugin invocation that the particular function fills
the role of initialization. Rename accordingly.
|
|
I haven't even compile-tested Linux and OSX-specific bits.
|
|
|
|
It's not annoying having to type it anymore. Also
"otr_boilerplate" -> "otr_module".
|
|
Polish speakers typically know English well enough and translations are
awkward.
|
|
|
|
|
|
|
|
|
|
Due to fucking AT&T vs BSD suit copyright defaults to all rights
reserved. Fuck Berne Convention as well.
|
|
Nice braino.
|
|
|
|
Adjust usages.
|
|
|
|
|