Re: some more issues with the new API

[Stefan Seefeld]

Just van Rossum wrote:
> 
> (Once more replying to my own post)
> 
> Stefan Seefeld wrote:
> >I'v a couple of other issues with FT2 which are mostly
> >naming and type conventions. One is the following:
> >
> >FT_Library is defined as a FT_LibraryRec_ *, yet
> >function take a pointer to a Library as argument,
> >thus you end up with a double indirection. Why is
> >FT_Library a pointer ?
> 
> I answered:
> >That's only true for FT_Init_FreeType, in which case it is a return value.
> >All other functions take a plain FT_Library.
> 
> That still doens't answer your question, does it? ;-)

Well, it did. I understand the trick concerning the internal pointer to
decouple the interface from the implementation. (A technique in C++ refered to
as 'pimpl')
I really just got confused by the FT_Init_FreeType call I guess...

Stefan

_______________________________________________________              
              
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: address@hidden

_______________________________________________________

      ...ich hab' noch einen Koffer in Berlin...