| yes, but in this case, the execution does not even get there.
Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland
> On 26 Dec 2016, at 19:25, Nate Whetsell wrote:
>
> For what it’s worth:
>
> * Format strings passed to prints appear to be parsed in printksset_ in OOps/ugrw1.c: https://github.com/csound/csound/search?q=printksset_+path%3AOOps+filename%3Augrw1.c. This function appears to still treat %n as a line feed (\n, U+000A) at https://github.com/csound/csound/blob/85bcd1658b766926511d8aef5d8ff8b1c1c34f0b/OOps/ugrw1.c#L920.
>
> * Between May 16, when Csound 6.07.0 was released (https://github.com/csound/csound/commit/2645994329cd2427af2f85d7c547dd2202cedfcd), and now, these commits changed OOps/ugrw1.c:
> * https://github.com/csound/csound/commit/d5c0efb9c8161a101532fad4176fd0e7f9b58856
> * https://github.com/csound/csound/commit/6825f2c28150b6cd827a9dd2027289783ad7ad90
> * https://github.com/csound/csound/commit/76c99b0cc4a37e552f2ff2c5d3461dcf0267e275
> * https://github.com/csound/csound/commit/7389b023dd59ab53117fb63704931b463220653c
> * https://github.com/csound/csound/commit/56688ed7c3e17c2a7249c242c8909954a7eb5b60
>
> I think it’s safe to say that OOps/ugrw1.c would benefit from increased |