In entry1.c I see the following:

  {  "changed.S", S(STRINDEX_OP),0, 3, "k",   "S",
     (SUBR) str_changed, (SUBR) str_changed_k, (SUBR) NULL       },

Does this mean we can now check for changes in strings? I see nothing
in the manual?

Sweet. It works. Just not documented it seems. Thanks for this.

On 23 January 2014 19:55, Rory Walsh  wrote:
> In entry1.c I see the following:
>
>   {  "changed.S", S(STRINDEX_OP),0, 3, "k",   "S",
>      (SUBR) str_changed, (SUBR) str_changed_k, (SUBR) NULL       },
>
> Does this mean we can now check for changes in strings? I see nothing
> in the manual?

thanks for publishing this. looks like reading the csound sources is 
your gute-nacht-lektüre ...
take care -
	joachim


Am 23.01.2014 22:24, schrieb Rory Walsh:
> Sweet. It works. Just not documented it seems. Thanks for this.
>
> On 23 January 2014 19:55, Rory Walsh  wrote:
>> In entry1.c I see the following:
>>
>>    {  "changed.S", S(STRINDEX_OP),0, 3, "k",   "S",
>>       (SUBR) str_changed, (SUBR) str_changed_k, (SUBR) NULL       },
>>
>> Does this mean we can now check for changes in strings? I see nothing
>> in the manual?
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

It's that or Das große Buch vom Räuber Grapsch, but at least I have a
dictionary for the book!


On 24 January 2014 18:37, joachim heintz  wrote:
> thanks for publishing this. looks like reading the csound sources is your
> gute-nacht-lektüre ...
> take care -
>         joachim
>
>
> Am 23.01.2014 22:24, schrieb Rory Walsh:
>>
>> Sweet. It works. Just not documented it seems. Thanks for this.
>>
>> On 23 January 2014 19:55, Rory Walsh  wrote:
>>>
>>> In entry1.c I see the following:
>>>
>>>    {  "changed.S", S(STRINDEX_OP),0, 3, "k",   "S",
>>>       (SUBR) str_changed, (SUBR) str_changed_k, (SUBR) NULL       },
>>>
>>> Does this mean we can now check for changes in strings? I see nothing
>>> in the manual?
>>
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>              https://sourceforge.net/p/csound/tickets/
>> csound5:
>>              https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>