Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| class MenuId: public KeyString {};
|
| class DialogId: public KeyString {};
|
|
| We need to take a decision now!
No we don't.
That's your opinion.
We are not in such a hurry.
This back and forth conversion tp/from utf8 during this transition phase
is a real hassle. Taking this decision now will simplify and speed-up
greatly the transition. We also need quickly the operator that Georg is
working on (+=, streams, etc).
| Please speak-up if you don't agree with that.
I am not sure that I agree with Andre (or you) that we have to use
docstring all over internally.
Neither am I sure it is wise to introduce a myriad of "new" string
types.
When do you think you will know your opinion? When you do, please
explain why it is not wise. I can very well imagine that these new types
could be extended depending on their use. Example:
class Format: public KeyString
{
public:
Format(bool supported = false): supported_(supported) {}
bool isSupported() { return supported_; }
private:
bool supported_;
};
Too many things remains stalled because you are not making up your mind.
You have the right to think that these are not important but I (and I
guess others) would like to turn the unicode page ASAP.
Abdel.
