I was looking at the code for Tag property in classes unit and noticed I can't
safely use Tag to keep runtime pointers (at least on a 64 bit compile). What is
the likelihood of getting tags changed to support universal access under 64/32
bit compiles?
What is the logic behind the shortfall? I
On Mon, 22 Nov 2010, Andrew Brunner wrote:
I was looking at the code for Tag property in classes unit and noticed I can't
safely use Tag to keep runtime pointers (at least on a 64 bit compile). What is
the likelihood of getting tags changed to support universal access under 64/32
bit
On Nov 22, 2010, at 9:13 AM, michael.vancann...@wisa.be wrote
The logic is that it is bad programming to use an integer to store a pointer.
And we don't want to encourage bad programming.
Yes, I know it's easy, and yes I know it's common practice. Neither make it
right to do so.
- michael vancanneyt michael.vancann...@wisa.be schreef:
On Mon, 22 Nov 2010, Andrew Brunner wrote:
I was looking at the code for Tag property in classes unit and
noticed I can't safely use Tag to keep runtime pointers (at least on a
64 bit compile). What is the likelihood of getting
On Mon, 22 Nov 2010, Andrew Brunner wrote:
On Nov 22, 2010, at 9:13 AM, michael.vancann...@wisa.be wrote
The logic is that it is bad programming to use an integer to store a pointer.
And we don't want to encourage bad programming.
Yes, I know it's easy, and yes I know it's common
michael.vancann...@wisa.be schrieb:
I was looking at the code for Tag property in classes unit and noticed
I can't safely use Tag to keep runtime pointers (at least on a 64 bit
compile). What is the likelihood of getting tags changed to support
universal access under 64/32 bit compiles?
On Mon, 22 Nov 2010, Hans-Peter Diettrich wrote:
michael.vancann...@wisa.be schrieb:
I was looking at the code for Tag property in classes unit and noticed I
can't safely use Tag to keep runtime pointers (at least on a 64 bit
compile). What is the likelihood of getting tags changed to
Hi,
http://bugs.freepascal.org/view.php?id=17384
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40838
can a C-ABI expert enlight us on this ABI mess.
Does this also effect calling in general of C-functions from Free Pascal.
regards,
Den Jean
___
michael.vancann...@wisa.be schrieb:
The logic is that it is bad programming to use an integer to store a
pointer.
That's why handles are used for that purpose, and on a 64 bit system
handles can have 64 bits as well.
Handles are equally bad. They are *not* pointers.
A user cannot know,
On Mon, Nov 22, 2010 at 5:13 PM, michael.vancann...@wisa.be wrote:
We'll fix the issue as the upcoming Delphi 64-bit - unfortunately - forces
us to follow suit.
Will it also create an additional confusion in design time? I mean, non-RAD
compilers possibly only have compile-time context,
10 matches
Mail list logo
