apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Garrett Rooney <roo...@electricjellyfish.net>
Subject Re: apr_dbd
Date Tue, 09 Aug 2005 19:14:56 GMT
Nick Kew wrote:
> Garrett Rooney wrote:
>>> The simple fix to (2) without breaking anything is to retain the
>>> existing get_entry as-is, and introduce an apr_dbd_get_typed_entry
>>> defined as above.  That would of course be an extra entry on the
>>> end of the apr_dbd_driver_t struct.
>> Can we really do that?  Adding an entry to the end of the 
>> apr_dbd_driver_t struct will change its size, and it's defined in a 
>> public header file, so I think that might be against our versioning 
>> guidelines, strictly speaking...
> Hmmm, really?  Retain both source and binary compatibility but can't
> release?

If you're adding a member to a struct that's defined in a public header 
file, how is that maintaining binary compatibility?  The size of the 
structure has changed, so anyone depending on that size is now broken.


View raw message