Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
vlz <[email protected]>
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <[email protected]> |
Ok, so a forward declaration with a typedef should work for you, should it not? I'd prefer it to exposing this. Would that be ok? Prof. Victor Lazzarini Maynooth University Ireland On 3 Dec 2024, at 17:23, Eduardo Moguillansky <[email protected]> wrote: It was used in the "poly" opcode, which can call an opcode multiple times ( https://csound-plugins.github.io/csound-plugins/opcodes/poly.html ). I took a look how I was using it. The code was accessing a pointer marked as OPCODINFO to see if the opcode given was a builtin opcode or a user defined one. I notice now that to check that I only need to see if the pointer is null. I was hoping to be able to use poly for user defined opcodes, but that is probably something which should be built into csound. On Tue, Dec 3, 2024 at 6:06 PM Victor Lazzarini <[email protected] > wrote: NB: I wasn’t aware this was used externally. I am not sure if it should actually be publicly available. None of our plugins had access to it. How is it used for? ======================== Prof. Victor Lazzarini Maynooth University Ireland > On 3 Dec 2024, at 16:59, Victor Lazzarini <[email protected] > wrote: > > a PR will put in back to public access. > ======================== > Prof. Victor Lazzarini > Maynooth University > Ireland > >> On 3 Dec 2024, at 15:45, Eduardo Moguillansky <[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, >> >> I have many builds failing because OPCODINFO seems to be gone missing. I see it in csoundCore.h, but it does not seem to be accessible for plugins. Other structs there >> are available, so I am a bit clueless. Any hints? >> >>