Re: The Synthizer Thread
C++ isn't a very fast-moving target, but there's incompatibilities between compilers and multiple standards. My guesses are that what's going on is some combination of me accidentally using VC++ extensions (i.e. VC++ is more forgiving about templates) and missing -std= flags (I think it's -std=c++11 or something, but on Windows the defaults are different). I'd start with trying to change the C++ standard explicitly to C++17, and make sure you're using at least Clang 9 (GCC should work if Clang does, but in the name of simplicity, etc).
Synthizer defines a PI in include/synthizer/math.hpp. I'd fix PI by including that header, not by moving to M_PI. I forget what the stupid difference is with Windows but M_PI gets strange and it's not worth dealing with it.
Beyond that you probably have to know enough C++ to spot the Microsoftisms, if it turns out to be that kind of thing.
I'm not willing to revert back past C++14 under any circumstances, and I'll need convincing before I revert back past C++17. Neither of those should be required, but in case you decide to go down that road for lack of other roads to go down, tell me why first and give me a chance to veto. C++11 and later started getting really big on offering actually useful things like atomics, threading, etc. and that trend has continued pretty steadily, so "You can't use insert-C++-standard" starts fundamentally shifting how I have to code the thing a lot.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
