Once again you have introduced changes to the Csound API that break
CsoundVST. Please be aware that CsoundVST is a part of "canonical csound".
I am not the only person who uses it.

I am going to fix up CsoundVST to work with the new API this time, but I
don't think I should have to keep doing this kind of thing.

I think there are two reasonable approaches here:

(1) Build and test CsoundVST along with any API changes in all its modes:
classic Csound, Python module, VST plugin, and so on.

(2) Keep the old API in place and working with "deprecated" notations,
giving me and any other API client developers a chance to rework our code
for the improved API at our convenience, and introduce your improvements as
additions instead of replacements.

I think (2) is preferable since it would also protect anyone else who is
developing to the API, and it would probably be less work for you also.
It's also the traditional approach for API developers.

 

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net