Re: sorting 5million minute data: choose std::list or std::vector
Leigh Johnston <leigh@i42.co.uk> wrote:
You can create a bug using any language feature. Fix and recompile.
Do you know how much does it cost to fix bugs vs. not having them in
the first place?
The problem is that the bug might not be found during development nor
even testing. And even if it's found in testing, it might be laborious to
track down the reason for the bug (because it often causes very erratic
behavior).
Besides, your argument can be used to defend sloppy programming. There's
nothing wrong in defensive programming that takes care of potential bugs
from the get go.
In these cases it actually makes more sense to have the width and height
as signed integers.
In your opinion.
Based on actual experience in actual projects where using unsigned integers
to denote width and height of images has bitten me hard.
So do I. I don't have any problem with casts; they are a perfectly
acceptable part of a statically typed language such as C++.
As long as you *remember* to cast everything that needs to be cast.
Again, explicit casting is often a sign of bad design. There are
situations where explicit casting is ok and to be expected, but this
isn't one.
Perhaps
Java is a more suitable language for you rather than C++.
Where did that come from?
As you seem to be in the "use int everywhere" camp Java may be a more
appropriate language for you.
No. I'm of the camp "use signed integers when signed types are being used".
I still don't understand what Java has to do with this.