A Dijous, 12 de novembre de 2009, Mathieu Malaterre va escriure: > On Thu, Nov 12, 2009 at 5:48 PM, Dominic Lachowicz > > <[email protected]> wrote: > > Just because a method is included in the "public" part of the class > > doesn't mean that it's part of poppler's supported, public API (i.e. > > Of course it is, this is exactly the definition. If you do not want to > expose it, put it in the protected section and make class friend. This > is basic C++. > > > meant to be used by 3rd-party users). The XPDF headers aren't > > installed by default - you need to configure with > > '--enable-xpdf-headers' to have them installed. > > I do not know those implementation details. > > > I believe that the recommended way of using poppler is through either > > the Qt or Glib bindings. > > This has absolutely nothing to do here. This is a matter of respection > versioning. Apparently work is properly done at library level and > SONAME/SOVERSION have been updated, all I am looking for is the same > at API level (ie. reflect the change of ABI/API, at code level). > > This is a very basic question: how does client application level cope > with an API incompatible change (this is a naive question, I could not > find the proper #ifdef)
And the very basic answer is that we don't support usage of those classes. Albert > > Thanks, > _______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
