Does anyone rely on pus and pop opcodes?
| Date | 2017-02-15 16:02 |
| From | jpff |
| Subject | Does anyone rely on pus and pop opcodes? |
These opcodes are deprecated but a significant bug has been identified
in them, relating to strings Unfortunately the author left the
community some time back and we do not have anyone experienced with
this code.
There are a number of things we could do:
1: Remove these opcodes (my preferred action)
2: Leave them in their broken state
3: Recruit someone to fix the code
4; Remove the string case and document it
5: Something else
Any thoughts? Anyone actually using it?
==John ffitch
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 | 2017-02-15 17:29 |
| From | Justin Smith |
| Subject | Re: Does anyone rely on pus and pop opcodes? |
I was considering using push and pop with some spectral opcodes recently (they are recommended in the documentation to work around the inability to pass some of the more obscure signal types as args to UDOs) On Wed, Feb 15, 2017 at 8:30 AM jpff <jpff@codemist.co.uk> wrote: These opcodes are deprecated but a significant bug has been identified |
| Date | 2017-02-15 18:13 |
| From | Steven Yi |
| Subject | Re: Does anyone rely on pus and pop opcodes? |
All signal types should work with UDOs today and it would be a bug to fix of not. I would prefer the removal of push/pop. On Wed, Feb 15, 2017, 12:29 PM Justin Smith <noisesmith@gmail.com> wrote:
|
| Date | 2017-02-15 18:39 |
| From | Justin Smith |
| Subject | Re: Does anyone rely on pus and pop opcodes? |
I see now that the opcodes in question have been marked deprecated in newer versions, and are marked as such in the documentation. On Wed, Feb 15, 2017 at 10:13 AM Steven Yi <stevenyi@gmail.com> wrote:
|