[LAD] [ann] CAPS 0.4.5

[Tim Goetze]

[David Robillard]
> No, the pragmatic thing to do is not deliberately break your plugin when
> several knowledgeable people have pointed out that doing so can cause countless
> problems.

Again: not the plugin is broken, but the host that assumes the port 
signature not to change over different plugin versions.

There is no mention of such a requirement in the interface 
specification, therefore the assumption is invalid and the 
responsibility for potential breakage lies with the host.

It has been shown that properly designed hosts handle the port 
addition just fine.

You may of course argue - not entirely unreasonably - that it is more 
pragmatic for the plugin author to cater for broken hosts than to 
expect them to be fixed.  Do you?

Tim