Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
| Lars> ... but I do not like it...
>
| I can understand that you do not like it, since it adds lots of
| #ifdefs.
I only added those to make it uglier.
| However, we could:
>
| 1/ add the .str().c_str() thingies unconditionally. Spotting and
| removing them later is not difficult. Or we could have a
| tostr(ostringstream) that does the right thing. Or...
but they are bad...
| 2/ we could have a lyx::regex class which is a simple wrapper (same
| semantics) around boost::regex that hides the complexity of these
| .c_str()
possible... but not nice.
| 3/ Is it possible to have an automatic contructor
| lyxstring::lyxstring(std::string const & s)
| and a lyxstring->basic_string convertor
| std::string lyxstring::operator()
one way perhaps, but not the other...
and not using contructors.
(nor operators)
| [please bear with my fuzzy C++ syntax notions...]
| The price to pay would be to include <string> everytime we use
| LString.h, but if we are lucky the amount of code generated would be
| minimal.
Is the need for lyxstring that _real_?
the last months should imply that it is not.
--
Lgb
