Re: vector::size_type
"James Kanze" <james.kanze@gmail.com> wrote in message
news:1192005924.349837.267620@19g2000hsx.googlegroups.com...
P.J. Plauger wrote:
"Kai-Uwe Bux" <jkherciueh@gmx.net> wrote in message
news:feh875$g8u$1@murdoch.acc.Virginia.EDU...
[...]
Btw, I have noticed that neither gcc nor VC++ require you
to write it like "std::size_t", but just "size_t" is ok
(without any 'using'). Is this also standard?
No.
It will be in C++0X, because it is de facto a widespread practice
in C++98.
It's the case in C++ 98 as well if you include <stddef.h>,
rather than <cstddef>.
My own rule to date has been to only use the .h forms of the
C headers, since I know what I'm getting with them.
[pjp] Do you? The C++ Standard says that the *.h forms must
declare all names in namespace std, then hoist them to the global
namespace with individual using declarations. A few meticulous
implementations do this, but most leave the *.h forms in their
traditional forms as inherited from older C compilers. So when
you include <stdio.h> you *might* get std::printf and printf,
or you *might* get just printf.
For the
<c...> forms, the standard said one thing, and all
implementations did something else, so I run the risk of
accidentally having code break when (or if) an
implementation does decide to become conform.
[pjp] Not all implementations, but most do. We can configure
our headers to fully conform or work the way our compiler
vendor customers want. Guess which way we choose.
Just curious, but with the change in the upcoming standard,
will there be any difference between the .h headers and the
<c...> headers. Or do we just have two different names for
the same thing for historical reasons.
[pjp] The new rule is:
-- If you want to assuredly declare printf, include <stdio.h>
(but you might also declare std::printf).
-- If you want to assuredly declare std::printf, include
<cstdio> (but you might also declare printf).
That happens to reflect the reality of *all* existing
implementations, so the next C++ Standard will actually
codify existing practice instead of trying to dictate a
practice that most vendors found they could not comply
with.
HTH,
P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com