Re: [ft-devel] web page for the forthcoming 2.2.0 release

[david turner]

Victor Luchits a écrit :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

  

Perhaps we shall *rename* the library to, say, `libft2', instead of
`libfreetype', together with a new API prefix `FT2_' instead of `FT_'.
This would avoid the whole mess.
    

Yeah, that and to keep binary compatibility a stub library could be
written as a replacement for an old libfreetype.so, which would just
dlopen the new .so and call appropriate functions. This is an ugly
solution but *should* work until a better solution is found.

What do you think?

  

I don't think you understand the problem. 2.2.0 is binary compatible with previous versions,
_except_ for a few rogue clients which access its internals directly:

• by calling some internal functions which are not available anymore.
• by peeking/poking at internal fields of public FreeType objects, and some of them have changed considerably
  

this cannot be fixed with a simple stub library, or we would have done it already.

Hope this helps,

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

- --
Best regards,
 Victor Luchits                mailto:address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD1BENdRaO3lCd98MRAnQ+AKDP9x2HlKQAsj3xZc9JZKltJSZ9VwCeKDCF
seml/TMLEIKJFcbAPNP2yu0=
=7q35
-----END PGP SIGNATURE-----


_______________________________________________
Freetype-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/freetype-devel

  

***********************************************************************************
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.
***********************************************************************************