Use of C++
#1682
Replies: 1 comment · 1 reply
-
No. Sry. Maintaining C becomes more and more a pain, compared to the functionality offered by modern languages like C++. Whenever I'll write new code, it will be written in C++11 now. Just like when I believe that existing code would benefit from C++, it will be ported to C++. Also, given that fluidsynth runs natively on (all?) POSIX platforms, I consider support for Wine as out of scope. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
OK, I understand. Thanks for clarification. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Thank you guys for your ongoing effort to develop FluidSynth.
I've noticed that in #1469, #1494 and #1620 some core files were converted from C to C++. While I understand the technical benefits C++ can offer, this change unfortunately prevents the Wine project from updating to newer versions of FluidSynth, as Wine does not accept C++ code. I've also identified a potential license compatibility issue with the new GCEM depencency (#1681).
I wanted to ask if switching these specific components back to C is a possibility you would consider? Wine only uses the core synth/DSP functionality, so it would be perfectly fine for the other parts (like the C++11 OSAL or DLS parser) to remain in C++.
I'm prepared to do the work to port the necessary components to C. Would you be open to reviewing such a pull request?
Thanks for your time and consideration.
Beta Was this translation helpful? Give feedback.
All reactions