Csound Csound-dev Csound-tekno Search About

[Csnd-dev] missing OPCODINFO

Date2024-12-03 15:45
FromEduardo Moguillansky
Subject[Csnd-dev] missing OPCODINFO
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?



Date2024-12-03 16:17
Fromvlz
SubjectRe: [Csnd-dev] missing OPCODINFO
I'll have a look. It might have been hidden.
Prof. Victor Lazzarini
Maynooth University
Ireland

> On 3 Dec 2024, at 15:46, Eduardo Moguillansky  wrote:
> 
> 
> 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?
> 
> 

Date2024-12-03 16:59
FromVictor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE>
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
a PR will put in back to public access.
========================
Prof. Victor Lazzarini
Maynooth University
Ireland

> On 3 Dec 2024, at 15:45, Eduardo Moguillansky  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?
> 
> 

Date2024-12-03 17:06
FromVictor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE>
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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  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?
>> 
>> 


Date2024-12-03 17:19
Fromvlz
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
Maybe a forward declaration is sufficient?

Prof. Victor Lazzarini
Maynooth University
Ireland

> On 3 Dec 2024, at 17:06, Victor Lazzarini <000010b17ddd988e-dmarc-request@listserv.heanet.ie> 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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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  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?
>>> 
>>> 
> 

Date2024-12-03 17:23
FromEduardo Moguillansky
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
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 <000010b17ddd988e-dmarc-request@listserv.heanet.ie> 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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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 <eduardo.moguillansky@GMAIL.COM> 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?
>>
>>


Date2024-12-03 17:39
Fromvlz
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
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 <eduardo.moguillansky@gmail.com> 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 <000010b17ddd988e-dmarc-request@listserv.heanet.ie> 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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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 <eduardo.moguillansky@GMAIL.COM> 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?
>>
>>


Date2024-12-03 17:40
FromEduardo Moguillansky
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
yes

On Tue, Dec 3, 2024 at 6:39 PM vlz <viclazzarini@gmail.com> wrote:
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 <eduardo.moguillansky@gmail.com> 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 <000010b17ddd988e-dmarc-request@listserv.heanet.ie> 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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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 <eduardo.moguillansky@GMAIL.COM> 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?
>>
>>


Date2024-12-03 18:39
Fromvlz
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
In which case, you could probably do that locally in your own code?

typedef struct opcodinfo OPCODINFO;

and no need for any change in the csound headers. What do you reckon?


Prof. Victor Lazzarini
Maynooth University
Ireland

On 3 Dec 2024, at 17:40, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:


yes

On Tue, Dec 3, 2024 at 6:39 PM vlz <viclazzarini@gmail.com> wrote:
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 <eduardo.moguillansky@gmail.com> 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 <000010b17ddd988e-dmarc-request@listserv.heanet.ie> 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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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 <eduardo.moguillansky@GMAIL.COM> 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?
>>
>>


Date2024-12-03 21:34
FromEduardo Moguillansky
SubjectRe: [Csnd-dev] [EXTERNAL] [Csnd-dev] missing OPCODINFO
yes; for now I think that works. Thanks for clarifying it anyway.

On Tue, Dec 3, 2024 at 7:39 PM vlz <viclazzarini@gmail.com> wrote:
In which case, you could probably do that locally in your own code?

typedef struct opcodinfo OPCODINFO;

and no need for any change in the csound headers. What do you reckon?


Prof. Victor Lazzarini
Maynooth University
Ireland

On 3 Dec 2024, at 17:40, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:


yes

On Tue, Dec 3, 2024 at 6:39 PM vlz <viclazzarini@gmail.com> wrote:
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 <eduardo.moguillansky@gmail.com> 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 <000010b17ddd988e-dmarc-request@listserv.heanet.ie> 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 <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> 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 <eduardo.moguillansky@GMAIL.COM> 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?
>>
>>