[Csnd] deprecated opcode warning
Date | 2019-07-31 11:19 |
From | Oeyvind Brandtsegg |
Subject | [Csnd] deprecated opcode warning |
Hi,
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
I just noticed this warning when running one of my csds. I understand that I probably have a deprecated opcode somewhere in my file, but unsure of how to identify it. all hints appreciated Oeyvind ''' Creating options Creating orchestra closing tag Creating score rtaudio: PortAudio module enabled ... using callback interface opcode deprecatedopcode deprecatedopcode deprecatedopcode deprecatedopcode deprecatedopcode deprecatedsorting score ... ... done ''' |
Date | 2019-07-31 16:56 |
From | john |
Subject | Re: [Csnd] deprecated opcode warning |
Attachments | |
That message cmes fro the semantic analysis; unfortunately the actual opcode name is not available to that code (will look at fixing that...) But the deprecated opcodes sould be reported elsewhere, in the parser where te full information should be printed. So I am not sure why yoiare not seeing that diagnostic I have a list of deprecated opcodes (attached) ==John ff On Wed, 31 Jul 2019, Oeyvind Brandtsegg wrote: > Hi, > I just noticed this warning when running one of my csds. > I understand that I probably have a deprecated opcode somewhere in my file, > but unsure of how to identify it. > all hints appreciated > Oeyvind > > ''' > Creating options > Creating orchestra > closing tag > Creating score > rtaudio: PortAudio module enabled ... > using callback interface > opcode deprecatedopcode deprecatedopcode deprecatedopcode deprecatedopcode > deprecatedopcode deprecatedsorting score ... > ... done > ''' > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2019-08-01 10:34 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] deprecated opcode warning |
Thanks for the help. I can find "changed.k" and "changed.S" in the list, and I do use changed as a function call changed() in my csd. Actually I use it six times, and the deprecatedopcode is also printed six times, perhaps a sign that it refers to these function calls in my csd? ... but I use the regular changed opcode, I am unsure of what the .k and .S means in the list of deprecated opcodes(?) best Oeyvind ons. 31. jul. 2019 kl. 17:56 skrev john <jpff@codemist.co.uk>: That message cmes fro the semantic analysis; unfortunately the actual |
Date | 2019-08-01 11:15 |
From | John ff |
Subject | Re: [Csnd] deprecated opcode warning |
The component after the . is not really the name but a tag that identifies which version of a polymorphic opcode is selected. I changed the development code to print the opcode name in the case you have. So it does look like changed is the deprecated opcode. Sent from TypeApp On Aug 1, 2019, 10:35, at 10:35, Oeyvind Brandtsegg |
Date | 2019-08-01 11:48 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] deprecated opcode warning |
Ok, thanks, but is changed really deprecated? Why would it be? tor. 1. aug. 2019 kl. 12:16 skrev John ff <jpff@codemist.co.uk>: The component after the . is not really the name but a tag that identifies which version of a polymorphic opcode is selected. |
Date | 2019-08-01 15:57 |
From | john |
Subject | Re: [Csnd] deprecated opcode warning |
changed was superseded by changed2 as it is more consistent on the first call. I think there is mistype in the manual for changed2 (ever=>never) On Thu, 1 Aug 2019, Oeyvind Brandtsegg wrote: > Ok, thanks,but is changed really deprecated? Why would it be? > > tor. 1. aug. 2019 kl. 12:16 skrev John ff |
Date | 2019-08-01 16:02 |
From | Victor Lazzarini |
Subject | Re: [Csnd] deprecated opcode warning |
Is it possible to make changed an alias of changed2, or maybe reuse it internally. That way we could remove the deprecated flag. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland > On 1 Aug 2019, at 15:58, john |
Date | 2019-08-01 16:20 |
From | Steven Yi |
Subject | Re: [Csnd] deprecated opcode warning |
I get deprecated warnings all the time with array(), which I prefer to use over fillarray in live coding as it's faster to type. Won't be an issue for CS7 where [] is part of the syntax, but the deprecated warnings are overkill in a live coding setting as they show up every time code that uses the opcode is evaluated and it becomes noise in the message output. I would like to see the message output for this be controllable with a flag. On Thu, Aug 1, 2019 at 11:02 AM Victor Lazzarini |
Date | 2019-08-01 16:24 |
From | john |
Subject | Re: [Csnd] deprecated opcode warning |
On Thu, 1 Aug 2019, Victor Lazzarini wrote: > Is it possible to make changed an alias of changed2, or maybe reuse it internally. That way we could remove the deprecated flag. > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > >> On 1 Aug 2019, at 15:58, john |
Date | 2019-08-01 16:28 |
From | john |
Subject | Re: [Csnd] deprecated opcode warning |
In newcode onre should not be using array but fillarray On Thu, 1 Aug 2019, Steven Yi wrote: > I get deprecated warnings all the time with array(), which I prefer to > use over fillarray in live coding as it's faster to type. Won't be an > issue for CS7 where [] is part of the syntax, but the deprecated > warnings are overkill in a live coding setting as they show up every > time code that uses the opcode is evaluated and it becomes noise in > the message output. I would like to see the message output for this > be controllable with a flag. > > On Thu, Aug 1, 2019 at 11:02 AM Victor Lazzarini |
Date | 2019-08-01 16:35 |
From | Victor Lazzarini |
Subject | Re: [Csnd] deprecated opcode warning |
ok, different semantics won't allow what I had in mind. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland > On 1 Aug 2019, at 16:24, john |
Date | 2019-08-01 16:44 |
From | Steven Yi |
Subject | Re: [Csnd] deprecated opcode warning |
That isn't the point and doesn't address my concern at all. On Thu, Aug 1, 2019 at 11:28 AM john |
Date | 2019-08-01 18:52 |
From | joachim heintz |
Subject | Re: [Csnd] deprecated opcode warning |
yes the behaviour is different: instr 1 kChanged changed 1 kChanged2 changed2 1 printk 0, kChanged printk 0, kChanged2 turnoff endin new alloc for instr 1: i 1 time 0.00000: 1.00000 i 1 time 0.00000: 0.00000 i think changed should not be marked as deprecated. changed2 is an extension, and gives different output at first k-cycle. j On 01/08/19 17:35, Victor Lazzarini wrote: > ok, different semantics won't allow what I had in mind. > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > >> On 1 Aug 2019, at 16:24, john |
Date | 2019-08-02 08:34 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] deprecated opcode warning |
I agree with this, and this way we also preserve backwards compatibility. tor. 1. aug. 2019 kl. 19:52 skrev joachim heintz <jh@joachimheintz.de>: yes the behaviour is different: |
Date | 2019-08-02 13:31 |
From | thorin kerr |
Subject | Re: [Csnd] deprecated opcode warning |
I second this. Thorin On Fri, 2 Aug. 2019, 1:20 am Steven Yi, <stevenyi@gmail.com> wrote: I get deprecated warnings all the time with array(), which I prefer to |