Re: [ft-devel] Source compatibility for 2.2.0

[Werner LEMBERG]

> 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: [...]
> 
> 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?

Personally, I prefer A).  This allows us to fix issues best IMHO, but
I'm probably alone with this opinion...

Unfortunately, I don't have time currently to work on FreeType, and I
won't have time the next few weeks either, I fear, because of some
deadlines.


    Werner