From: Toon Knapen (toon_at_[hidden])
Date: 2001-07-05 15:07:33
David Abrahams wrote:
> ----- Original Message -----
> From: "Toon Knapen" <toon_at_[hidden]>
> > using get_* from time to time is the worst option. Since you won't
> > remember when you've added the get_ and when you did not you'll be
> > forced to look to the doc everty time again. Also this makes code really
> > ugly. Guidelines should at least provide some uniformity !! Same goes
> > for synonyms, first you'll have to think about a good synonym while
> > coding and users will never see the connection between both
> > Adding the *_t is also ugly I think.
> > But as I'm apparantly the only one who feels this way, I can't believe
> > nobody encountered this problem already, I'll rest my case.
> No, I agree with you completely on the points above. I only question whether
> it is worth changing everything we've done at this point.
I've been involved in several development project with a lifetime of at
least five years and the day the development team is resistant to
'incompatible' modifications and preventing better engineering, well
from that day onward the project is doomed. A few years later they're
working with ancient technology.
Well this is somewhat of a heavy statement in this case. My point is
that the argument that you will break some existing code, which you btw
can fix very rapidly and easily, is negligable (to me at least)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk