Re: code style in the vfs

[Oswald Buddenhagen <ossi kde org>]

On Sun, Sep 26, 2004 at 07:13:40PM +0200, Pavel Tsekov wrote:
> Then blaming it to those bad functions - strchr() and friends.
> 
yes.

> > guess why c++ has "const in, const out" and a "non-const in,
> > non-const out" versions of these functions?
> 
> Why don't you enlighten me ?
>
a function that silently casts away a const cannot be good. it's been
done this way for compatibility, but it sucks.

> Do you imply that one cannot write good and robust C code if he/she
> haven't heard of C++ .
> 
no. but seeing what others did helps.

> > in c one can't overload, so one has to accept some inconvenience to
> > produce safe code.
> 
> Writing safe code thanks to overloading - wow!
>
save your sarcasm for somebody else. that's _my_ domain. :-)=)
and now think again.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.