chnget:k(…)
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 4 Mar 2017, at 16:39, Dave Seidel  wrote:
> 
> I am working on a csd with a bunch of control channels, and when I switched from
> 
> k1 chnget "foo"
> 
> to
> 
> k1 = chnget("foo")
> 
> it stopped working. I've experienced this with a few other opcodes as well Is there a list somewhere of opcode that don't work with function syntax? I understand that opcodes with multiple outputs are not expected to work, but chnget doesn't seem to fall into that category. 
> 
> - Dave
> 
> -- 
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 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

in this case, because both

k1 = ivar

and

k1 = kvar

are valid, the compiler can’t tell which one of polymorphic opcode forms 
the user wants and falls back to chnset:i(). So we need the type hint.

========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 4 Mar 2017, at 16:51, Aaron Krister Johnson  wrote:
> 
> Dave, now that you mention it: I'm curious why multiple outputs couldn't be designed to work, a la Python?
> 
> In Python, you can have a function that returns a tuple or list, etc. etc.
> 
> e.g.:
> 
> alpha, beta = myfunction(gamma, theta)
> 
> 
> 
> Aaron Krister Johnson
> http://www.untwelve.org
> 
> On Sat, Mar 4, 2017 at 10:39 AM, Dave Seidel  wrote:
> I am working on a csd with a bunch of control channels, and when I switched from
> 
> k1 chnget "foo"
> 
> to
> 
> k1 = chnget("foo")
> 
> it stopped working. I've experienced this with a few other opcodes as well Is there a list somewhere of opcode that don't work with function syntax? I understand that opcodes with multiple outputs are not expected to work, but chnget doesn't seem to fall into that category. 
> 
> - Dave
> 
> -- 
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 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


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

Well the x,y = opcodes() does work in the parser3 branch.