Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] RFC: OENTRY refactor
john <[email protected]>
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <[email protected]> |
I am not sure what the advantage is. I remember I got rid of aoptr some time back but it broke the C++ template -- never understood why. A lot of editing for little gan? On Wed, 3 Jan 2024, Victor Lazzarini wrote: > Sounds good to me. It’s quite a big change though we’ll need make throughout the code to replace all the OENTRY etc > (we’ll also have to think about the plugins in the plugins repo and update those for this). > > ======================== > Prof. Victor Lazzarini > Maynooth University > Ireland > >> On 3 Jan 2024, at 22:42, Steven Yi <[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. >> Hi All, >> >> I was looking at OENTRY and think we can make a change to simplify it by: >> >> 1. Remove .thread >> 2. Remove .aopadr >> 3. Rename .iopadr to initFunc >> 4. Rename .kopadr to perfFunc >> >> There's little code to check ->thread and I think it can be refactored to check the presence of initFunc or perfFunc. I think initFunc and perfFunc might be a little easier to understand for modern devs vs. iopadr and kopadr. >> >> Thoughts? >> >> Steven > >