Jean

The reason curlpp might work now as a library is because it doesn't use templates with user defined types at all. And even in case of setOpt all arguments are either of type OptionBase or OptionBase or OptionList. Below are 3 exports from curlpp dll lib which are responsible for this

void cURLpp::Easy::setOpt(class cURLpp::OptionBase const &)
void cURLpp::Easy::setOpt(class cURLpp::OptionList const &)
void cURLpp::Easy::setOpt(class cURLpp::OptionBase *)

If we are going to add the new setOpt() and set() functions taking as an argument the real type of option's type then we'll have to explicit instantiate both of these functions with all possible options' types.

template
CURLAPI set<Options::Url>(std::string const & value);
template
CURLAPI set<Options::SslVerifyHost>(long const & value);
template
CURLAPI set<Options::SslVerifyPeer>(bool const & value);
etc.

I'm not sure if even in the current source there aren't places where we should have made explicit instantiations that would generate all needed by users code in the library object file instead of generating it in user's application object file.

Regards
Piotr

_______________________________________________
cURLpp mailing list
cURLpp_at_rrette.com
http://www.rrette.com/mailman/listinfo/curlpp
Received on 2008-11-22