[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: HEADS UP: API error code changes

At 06:53 AM 12/13/2003, Pierangelo Masarati wrote:
>Kurt D. Zeilenga wrote:
>>At 11:14 PM 12/12/2003, Luke Howard wrote:
>>>And applications will need to be recompiled against a new libldap;
>>>I know this is easy to force by bumping up the shared library
>>>version number, but it would be nice if this could be avoided. 
>>It cannot be avoided.  We have actual conflicts between
>>API codes and official assigned protocol result codes
>>which requires and resolving this requires we move the
>>API codes.
>What if we use negative API codes only in HEAD,
>and we dpn't release with them?

Then our release API cannot be extended by applications
to take advantage of the conflicting protocol result codes.

>It'll take a bit
>more to detect conflicts, but at least only beta
>testers would be affected (or, to state it
>differently) cooperation in debugging would be on
>a voluntary base ...)

I think the only reasonable solution is to raise the
library "current" version.  I was thinking of setting
it to "202" (for 2.2).