Re: [Csnd-dev] C++ wrapper
Michael Gogins <[email protected]>
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <CAFswGP3c0SQbgF3=5Mr-bJpaS8enqAdZEt-GJ54oU=4cZsLEQA@mail.gmail.com> |
I do not care either way. However, I do care that the C++ threading code should be in the same header file as all the other C++ declarations. ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Jul 27, 2024 at 10:04 AM Rory Walsh <[email protected]> wrote: > I'm not against the idea, but I do like the fact that all the C++ stuff is > in one dedicated header file. I think it makes things cleaner, and also > makes it a little easier to navigate when browsing for functions. I can > also see how consolidating them might make things simpler in terms of > maintenance. Therefore I'm happy to go with the flow on this. > > On Sat, 27 Jul 2024 at 15:53, Tarmo Johannes <[email protected]> wrote: > >> Hi! >> >> I can't think of any objections, sounds like good plan to me. >> >> Tarmo >> >> L, 27. juuli 2024 16:01 Victor Lazzarini < >> [email protected]> kirjutas: >> >>> While syncing the C++ wrapper, it occurred to me that it could be more >>> convenient to place it in the same header as the C API under C++ guards, >>> >>> - it would be simpler to keep it in line with C API >>> - hosts only include csound.h in C or in C++ >>> >>> Should we move to that arrangement? >> >>