Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] C++ wrapper

For running csound in a separate thread.

On Sat, Jul 27, 2024, 12:07 Victor Lazzarini <
[email protected]> wrote:

> Which C++ threading code?
>
> > On 27 Jul 2024, at 16:36, Michael Gogins <[email protected]>
> wrote:
> >
> > *Warning*
> > This email originated from outside of Maynooth University's Mail System.
> Do not reply, click links or open attachments unless you recognise the
> sender and know the content is safe.
> > 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?
>
>