Re: [libxml++] libxml++ future - strings and overloaded helper functions

[Matt Esterly <matt automaticduck com>]

Looks great!  A couple ideas I would be will to submit patches for
a)   Support of std::stringw in addition to std::string

b) Overloaded element functions which do conversions from primitives  
to strings for the caller
for example:
int n;
elem->add_content(n);

If people don't like b maybe an overloaded class which supports the 
function overloads..

BTW I am able to successfully able to use libxml++ on Linux, MacOSX, 
and win32 nice work!

On Thursday, September 25, 2003, at 03:42  PM, Christophe de Vienne 
wrote:

> Instead, we would explicitely instanciate the template classes into the
> dynamic lib with a chosen string type (very probably Glib::ustring). 
> Programs
> using this default string type wouldn't need to be recompiled at each 
> minor
> release, which is the main argument against templates.
> At the same time, users who want to use another string type (QString 
> for
> exemple, or even std::string of char *), could still do it, at the 
> price of
> recompiling their application at each release of libxml++, even if the 
> API
> doesn't change.
>
> - - Is this solution acceptable for you ?
> - - Is there any issue about LGPL with template libraries ?