freetype
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [ft] ABI "stability" question.


From: Turner, David
Subject: RE: [ft] ABI "stability" question.
Date: Thu, 27 Oct 2005 14:30:41 +0200

>
> Have there been any changes in the abi that would cause programs to
> break if the were linked with older libraries?
>
> I guess the real question is, when was the last time this
> happened? I've
> been reading the ChangeLogs and I don't see anything jumping
> out at me.
>

Regarding the public API, I think that the last one was when we
added some fields to the FT_Bitmap_Size structure. This was _really_
bad. I think it was around 2.1.5 or 2.1.7

Some public APIs we consider experimental or in beta have changed
though: the Cache subsystem and the style synthetizer I believe.

Apart from that, I don't remember anything from a long time, though I
may be wrong.

Regarding the internals, a _lot_ have changed, and this has broken
many third-party libraries which took the liberty of including the
FreeType internal headers to peek at useful data instead of asking
for a specific API or providing a patch.

And this has repeatedly broken fontconfig, libXft, Pango and a few
others.

Life's fun :-)

- David Turner
- The FreeType Project  (www.freetype.org)


> Thanks.
>
> --
> Hisashi T Fujinaka - address@hidden
> BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) +
> $2.50 = latte
>
>
> _______________________________________________
> Freetype mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/freetype
>
***********************************************************************************
Information contained in this email message is confidential and may be 
privileged, and is intended only for use of the individual or entity named 
above. If the reader of this message is not the intended recipient, or the 
employee or agent responsible to deliver it to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please immediately notify the address@hidden and destroy the original 
message.
***********************************************************************************





reply via email to

[Prev in Thread] Current Thread [Next in Thread]