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.
|
|
|
|
I haven't even compile-tested Linux and OSX-specific bits.
|
|
|
|
|
|
The initial version won't have a generalized spline
with multiple parameters to configure the gain. But
it's doable in one go unlike a fully-fledged version
from the start.
|
|
|
|
|
|
|
|
|
|
We heavily used "volatile bool" to check if the thread
loop should stop. But this functionality is already
provided by Qt5's QThread::requestInterruption.
In other cases, "volatile" is wonderfully
underspecified so it's better to ditch its usage in
favor of std::atomic<t>. At the time we don't appear to
be using the "volatile" keyword except when calling
win32's Interlocked*() family of functions as
necessary.
In freetrackclient's header the "volatile" qualifier
was used as part of a typedef. This doesn't work. Use
it as part of data declaration.
|
|
|
|
Adjust usages.
|
|
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.
|
|
|
|
|
|
|
|
|
|
Needs the spline class to allow initializing itself from a function. Even if the
passed control points are correct, it still looks like shit. Presently they
aren't correct though. Need to work on linear approximation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It doesn't work good enough.
Try use splines instead.
|
|
|