Not sure if this has already been done or not. Perhaps we should consider writing test-cases for each example in the manual, and use a script to run all the tests prior to the release of a new version of Csound. This would help smooth things out for beginners, as they are less likely to run into buggy examples. This might even help catch bigs introduced into Csound during the development process.
I might have time to do this myself sometime in the next few months. If anyone is interested in starting a dialog about how to tackle this, no better time than the present.
Best,
Jake
jpff-2 wrote:
>
> Dear all,
> i'm trying all the examples of the manual. Can be useful for You if i will
> make a report (as possible for me) of not working examples? I would like
> to
> be helpful for You, but i have not ability! I'm not a programmer, i'm not
> an
> expert in csound ... I have only some free time.
> If i can be useful let me know, if not, don't worry, i'll be always here
> to
> ask You for some help.
>
Sure; all examples worked at one time byut things drift. Knowing of ANY
problems in the manual or the system is good; which is not a promise to
fix everything.... but we do try to fix stuff whenever it turns up.
==John ff
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
