Re: [Re: [libxml++] UTF8 support]



Jonathan Wakely wrote:

To use different template params a user would have to either:
* recompile the library so it explicitly instantiates the templates with
  their choice of params. Maybe this could be done using clever configure
  tricks, so when a new release of the lib is made the user configures
  it to use their choice of string, and then just relink their apps to
  the new lib.

I don't think this is an option (at least not the way you suggest it):

what would it mean to have libxml++ installed ? From a packaging point of view you'd have to ask 'is libxml++-with-glib::ustring' installed ?

In the light of this, if it is really decided to use a templated version
of libxml++ *and* hide that behind a wrapper, you would have to have that wrapper be explicit, i.e. something like 'glibxml++' (being the libxml++ library for use with the other 'g libraries'), or 'qlibxml++',
the version now compiled for use with Qt, etc., etc.

or
* include the definitions into their code directly, which means users
  must recompile their apps every time the definitions change.

yeah, that's the simple solution I originally suggested, but which was
rejected from people concerned about package maintenance.

Stefan





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]