Why does API change from version to version?
Posted: 23 Jun 2010 23:43
I'm programming a C# interface against the libVLC API.
I recognized, that the API changes from (sub)version to (sub)version, what makes it difficult and time-consuming to keep the c# interface up-to-date.
In the new version 1.1.0 not only the API functions and functionality changed, but also the existing enumeration values changed ...
Why is it not possible to define an API where only the code-behind changes? Or at least keep the changes as small as possible?
I recognized, that the API changes from (sub)version to (sub)version, what makes it difficult and time-consuming to keep the c# interface up-to-date.
In the new version 1.1.0 not only the API functions and functionality changed, but also the existing enumeration values changed ...
Why is it not possible to define an API where only the code-behind changes? Or at least keep the changes as small as possible?