[Cs-dev] invalue/outvalue: still supported in cs6?
| Date | 2013-06-17 15:50 |
| From | Richard Henninger |
| Subject | [Cs-dev] invalue/outvalue: still supported in cs6? |
| Attachments | None None |
|
There is a statement in “What_is_New.txt” that invalue, outvalue and channel callbacks and for setters for all these have been removed.
Since they are still very much present and functioning in RC3, I am wondering whether 1) they are only being deprecated, 2) the statement in What_is_New is no longer true and should be removed, or 3) their removal’s not yet occurring was an oversight?
I’ve searched for discussions of this and haven’t found any definitive statements one way or the other.
What is their fate really? Should we stop using them in cs6 hosts and use the new thread-safe signatures exclusively for channel interaction?
Richard Henninger
richard@rghmusic.com |
| Date | 2013-06-17 21:23 |
| From | Andres Cabrera |
| Subject | Re: [Cs-dev] invalue/outvalue: still supported in cs6? |
| Attachments | None None |
Hi, They were removed, but then put back. I think it is useful to have both methods in the API to allow for both synchronous and asynchronous channel access. The only big change is that both invalue/outvalue and chnget/chnset now operate on the same channels, where they would be separate before. (When the callbacks were removed, the invalue/outvalue opcodes operated just as chnget/chnset without callbacks, so the opcodes were never deprecated). One of the advantages of the callback based method is that it is inherently thread safe, so there is no need for locking.Andrés On Mon, Jun 17, 2013 at 7:50 AM, Richard Henninger <richard@rghmusic.com> wrote:
|
| Date | 2013-06-17 21:34 |
| From | Richard Henninger |
| Subject | Re: [Cs-dev] invalue/outvalue: still supported in cs6? |
| Attachments | None None |
|
Thanks for the clarification, Andres.
I suspect that the sentence in What_is_New.txt on the sourceforge csound6 site announcing their elimination should itself be removed before 6’s final release.
Richard Henninger
richard@rghmusic.com From: Andres
Cabrera
Sent: Monday, June 17, 2013 4:24 PM To: Developer discussions Hi,
They were removed, but then put back. I think it is useful to have both methods in the API to allow for both synchronous and asynchronous channel access. The only big change is that both invalue/outvalue and chnget/chnset now operate on the same channels, where
they would be separate before. (When the callbacks were removed, the invalue/outvalue opcodes operated just as chnget/chnset without callbacks, so the opcodes were never deprecated). One of the advantages of the callback based method is that it is inherently
thread safe, so there is no need for locking.Andrés On Mon, Jun 17, 2013 at 7:50 AM, Richard Henninger
<richard@rghmusic.com> wrote:
|
| Date | 2013-06-17 21:47 |
| From | Victor Lazzarini |
| Subject | Re: [Cs-dev] invalue/outvalue: still supported in cs6? |
| Attachments | None None |
I would suggest not to use invalue/outvalue. I think the other system is much better; with strings in particular, you have more flexibility. I have looked at the invalue with strings issue, and as I suspected, the opcodes were out of step with the new string code. I am fixing this, but strings will not be dynamic and their size will be limited to 256 chars (this is not the case elsewhere). I would appreciate if Andres could revise my code, as I am not too sure about how these opcodes are supposed to work in the new system. Victor On 17 Jun 2013, at 21:34, Richard Henninger wrote:
Dr Victor Lazzarini Senior Lecturer Dept. of Music NUI Maynooth Ireland tel.: +353 1 708 3545 Victor dot Lazzarini AT nuim dot ie |
| Date | 2013-06-19 00:51 |
| From | Andres Cabrera |
| Subject | Re: [Cs-dev] invalue/outvalue: still supported in cs6? |
| Attachments | None None |
Thanks. This looks fine and the tests are passing OK. Cheers, Andrés On Mon, Jun 17, 2013 at 10:47 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
|