Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| Lars> if (disp == ascii_guill) ...
|
| This I do not like much. This hides the meaning of the code,
| especially since I have a
| else if (disp == ">>")
| two lines after. A piece of trivial code is going to be changed to
| something not so nice.
If you give a nice name to ascii_guill I'd think that the code could
be even clearer than it is now.
I am not sure that you can have you cake and eat it at all times...
unicode is more cumbersome to work with.
| Lars> Or we can create a operator==(docstring const &, char *)
|
| I thing I would like that.
|
| Another point is that we make a great use of ostringstream for
| handling strings. I'd like to have something comparable for docstring
| (to which I can send C strings if needed maybe).
ostringstream will be a challenge...
(or perhaps not... we might be able to create a odocstringstream kindo
thing easily.)
| I am perhaps overestimating the number of cases where it is needed...
I hope so.
--
Lgb
