[ft-devel] Source compatibility for 2.2.0

[Owen Taylor]

Leaving aside the question of soname and binary compatibility,
I was surprised to see in CVS the change to FT_Outline_MoveToFunc
and friends; from the CVS commit message:

===
The next release will be 2.2.0, so don't worry about source code
backwards compatibility.

* include/freetype/ftimage.h (FT_Outline_MoveToFunc,
FT_Outline_LineToFunc, FT_Outline_ConicToFunc,
FT_Outline_CubicToFunc, FT_SpanFunc, FT_Raster_RenderFunc),
include/freetype/ftrender.h (FT_Glyph_TransformFunc,
FT_Renderer_RenderFunc, FT_Renderer_TransformFunc): Decorate
parameters with `const' where appropriate.
===

Such a change means that a project like Cairo either has to:

 A) Choose to compile *only* with 2.2.0 or newer

 B) Use ugly #defines to try and compile with both

Is that really the intention?

Thanks,
                                        Owen

signature.asc
Description: This is a digitally signed message part