size_t, size_t, wherefore art thou aliased?

[Steve Horne]

On Wed, 20 Sep 2006 08:15:29 -0700, Gregor Richards
<Richards at codu.org> wrote:

>The most unfortunate thing about this is that there's virtually no way 
>for a programmer on a 32-bit system to know when they've ran into a bug 
>like this.  Yuck.

In Visual C++, you get warnings about size issues even when they don't
exist. VC++ will complain if it thinks the type you specified might be
a 64 bit type in the future, and your using it somewhere 32-bitty for
instance.

Maybe a similar (optional) compiler warning? The compiler could flag
'this is being treated as an uint32_t/uint64_t but it was originally
size_t' and give warnings as needed?

-- 
Remove 'wants' and 'nospam' from e-mail.