[ofw] [PATCH] Bump up CI and AL interface version numbers
    Fab Tillier 
    ftillier at windows.microsoft.com
       
    Tue Aug 26 13:35:20 PDT 2008
    
    
  
> Consider this differently.  Suppose that you're creating a new API.
> You implement ib_open_al() and ib_close_al(), commit the changes, and
> call it API 1.  You add ib_open_ca() and ib_close_ca() - API 2.
> Ib_alloc_pd(), ib_close_pd() - API 3... and so on until you finally
> release the API as version 48.  Checking code into source control != an
> API version.
I agree with you here, but that's entirely different than making backward-incompatible changes to an existing API.
So an appropriate example would be you implement ib_query_ca, call it API 1.  You have this API working for a while, clients exist making use of it.  You now change the structure that ib_query_ca returns so that using it as if it was API 1 will cause clients (which now exist) to dereference bogus memory.  Is it still API 1?
-Fab
    
    
More information about the ofw
mailing list