> I think that exceptions can help make code better readable and I'd
> suggest using them if possible (since programmers tend to be used to
^^^^^^^^ you mean 'necessary', do you?
> java as well, this is probably not a big proglem).
Java programmers tend to be a problem ;-} Seriously, as long as you
don't need a feature, don't use it.
> Ah, by the way, what was the deal to use 'char const *' instead of
> 'const char *' ? I know, the former is probably a bit more correct from
> the thinking, but whereever you look, 'const char *' is used .. so it
> bocomes more confusing.
As you noticed there are some tiny advantages for 'T const *', so there
seems to be no reason _not_ to use it. Personally I don't have problems
with 'const T *', since that's the way I am writing my own code. If you
work on different projects you need to get used to different styles
anyway... I doubt people would be amused if I'd try to force them to switch
over to my "own" indentation and bracketing style ;-}
The big deal is 'uniformity'. Code should be uniform throughout a project -
or at least throughout large parts of a project. Once the rules are set,
people are expected to stick to them - unless there are obviously wrong or
outdated. And I doubt there are many rules used in the newer parts of
LyX that are _obviously_ wrong...
> And it is less confusing if you actually have a const pointer to a
> const string 'const char * const' ..
You are not supposed to use char * for strings anyway, and I am not aware
of similar contructs for other types used in LyX.
> (and I should really work on my diploma thesis ..)
Oh come on... Friday is the day of complaints ;-)
Andre'
--
André Pönitz ........................................ [EMAIL PROTECTED]
