Re: Visual Studio 2005 x64 mode.
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Thu, 8 May 2008 07:45:17 -0400
"Tim Roberts" <timr@xxxxxxxxx> wrote in message
news:nv7524dtsq7k54scbbsa6e40r5r2js6glr@xxxxxxx
stevensmith1010@xxxxxxxxx wrote:
Hi Dave,
the problem is I have a very huge code and to manually go and change
to __int64 would be very tedious....so thats why was thinking if
there are some kind of compiler switches to force ints as
__int64's...?
Nope. In an intuitive world, "long" would be 64 bits in a 64-bit
compilation, as it is in gcc, but Microsoft decided we were all too
stupid to handle that. In my opinion, that was a huge mistake.
I'm not sure I understand. long _is_ 64-bit in a 64-bit build, just like
in GCC. What again are you complaining about?
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: Visual Studio 2005 x64 mode.
- From: Tim Roberts
- Re: Visual Studio 2005 x64 mode.
- From: Alex Blekhman
- Re: Visual Studio 2005 x64 mode.
- References:
- Visual Studio 2005 x64 mode.
- From: stevensmith1010
- Re: Visual Studio 2005 x64 mode.
- From: David Lowndes
- Re: Visual Studio 2005 x64 mode.
- From: stevensmith1010
- Re: Visual Studio 2005 x64 mode.
- From: Tim Roberts
- Visual Studio 2005 x64 mode.
- Prev by Date: Re: C2664 on initializing auto_ptr with const patam in constructor
- Next by Date: Re: Offset by 1 in CStdiofile Seek while reading 0xa
- Previous by thread: Re: Visual Studio 2005 x64 mode.
- Next by thread: Re: Visual Studio 2005 x64 mode.
- Index(es):
Relevant Pages
|
