Re: 64 bit data types
- From: "Roger Lascelles" <rogerlasAToptusnet.com.au>
- Date: Tue, 31 Jan 2006 10:09:20 +1100
"Florent Ouchet" <ouchet.florent@xxxxxxxxxxx> wrote in message
news:43de9507@xxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> > According to MS's and AMD's recommendations, generic integer *data*
> > types, ie. Integer and Cardinal, should remain 32 bits, leaving 64 bit
> > to explicit 64 bit types.
>
> That's very bad news for libraries that need to compile on various
> platforms (32 bits and 64 bits), many lines will have to be rewritten :(
Unless you are casting pointers to integers or longints, there shouldn't be
much trouble. We have always known that such a cast is liable to run in to
trouble. I think we will be able to write code and libraries which compile
32/64 bit with no trouble.
You can still store a 32 bit integer in a 64 bit object reference or pointer
variable: e.g. in a TList.
I suspect I have zero problems in my own code. Imagine how much strife a
bad C programmer will have, with a typecast on every 3rd line ! At least
they will get compiler warnings, I assume.
Roger Lascelles
.
- References:
- 64 bit data types
- From: Florent Ouchet
- Re: 64 bit data types
- From: Eric Grange
- Re: 64 bit data types
- From: Florent Ouchet
- 64 bit data types
- Prev by Date: Re: 64 bit data types
- Next by Date: Runtime design forms support
- Previous by thread: Re: 64 bit data types
- Next by thread: Re: 64 bit data types
- Index(es):
Relevant Pages
|