Hi everybody, I would also like to see some enhancement in this issue. I think it is mainly a question of style, but my codebase is full of calls to c_str() for this reason.
I do not like the idea of configuring at compile time, this will just add some preprocessor acrobatics to the headers. I would prefer to have all the comparison operators that are provided for std::strings, and I would implement them as free functions that live in a different header file. Those who do not want them need not #include them. cheers, Rupert > > > So, to summarize my new proposal: in case you don't have a > decision, or that you're inclined not to include it, may I propose > that you include these features as *optional* features that could > be enabled at configure-time? I'm talking about: > > ./configure --enable-implicit-string > > or > > ./configure --enable-operator==string > > People could decide to enable them o not, and those who > enable them could later provide feedback on whether they > found it useful, whether they encountered any inconveniences > or more serious trouble, etc. > > Seems like a very-low-risk move, but one that I estimate a > few (or even more than a few) people will find it useful. > > Thanks, > > Carlos > -- -- Rupert Kittinger-Sereinig <[EMAIL PROTECTED]> Krenngasse 32 A-8010 Graz Austria _______________________________________________ Libpqxx-general mailing list Libpqxx-general@gborg.postgresql.org http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
