Not really. It's not done by simply switching to a C++ compiler. The data
types should be converted to object-oriented ones and the
checking-every-functions-return-value-mentality should be rethought. Usage
of STL containers would need to be considered in order to unleash C++ whole
power. And we wo
damn! and I guess moving to C++11 is not an option
On Fri, Oct 6, 2017 at 5:55 PM, Tom M. wrote:
> This is for C++11 only.
>
> And as I just learned: The threading part of C11 is optional, which is
> very disappointing. Because it means that even though clang and gcc claim
> to be feature comple
This is for C++11 only.
And as I just learned: The threading part of C11 is optional, which is very
disappointing. Because it means that even though clang and gcc claim to be
feature complete, glibc is (still) lacking support for the IMO most
important part of C11: Threading ( see
https://sourcewa
According to https://msdn.microsoft.com/en-us/library/hh567368.aspx
VS2015 should have decent enough C11 support for threads and atomics.
Or is only for C++11 ?
Philippe
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/li
I see, and because that __declspec() stuff is handled via the
FLUIDSYNTH_API macro, I believe it's ok to just ignore fvisibility then.
Thanks!
Tom
2017-10-06 10:59 GMT+02:00 KO Myung-Hun :
> Hi/2.
>
> fvisibility is ignored on Windows as well as OS/2. Instead, on those
> platforms, something s
Hi/2.fvisibility is ignored on Windows as well as OS/2. Instead, on those platforms, something such as__declspec(dllexport) and __declspec(dllimport) may be used.I attach 4 patches.KO Myung-Hun--- Original message - From : "Tom M." To : "FluidSynth mailing list" CC : Date
Oh, I was expecting to see the metadata in the text right before the
patches, but as it seems they were embedded in the email itself. Anyway,
yes please send them again as attached files.
If you're using 4.9 I dont quite understand why fvisibility is ignored. Is
this a general OS/2 problem? Or jus
