|
VBBR
Moderator
Brazil
617 Posts |
 Posted - Jun 13 2004 : 10:12:12 AM
|
quote:
and for Long it's = 8 byte as Double in vb.6
That's wrong, because a Double is a floating-point value but a Long is an integer number.
quote:
and the definition is not stable ,,it depens on wither it's 32-bit or 64-bit
Right, but for C++ only. VB6 and .NET currently only work with the Win32 platform, that is, 32 bits. (4 bytes)
(I dunno how would one write a 64-bit application in VB. I guess it's impossible.)
|
Whatever. Who knows... |
 |
|
|
game_maker
Knave
Saudi Arabia
83 Posts |
Posted - Jun 13 2004 : 7:46:40 PM
|
Dan:
Yes they have to make every definition consistence with every language specially on .Net FrameWork ,,, and they have to expand the ability of Integers types ... and VB.Net made from C# (as I heard) ... etc
But still if you asked me what is better :
1) defining LongInteger (8-bit) or what ever they name it
2) changeing the definition for Integer Type and Long Type
So, Clearly I will prefare 1 over 2 
VBBR :
You are very right ,,, in VB.Net they are difference in representation but they are now both (8 bytes) and this what I ment  |
|
|
|
|
FPS Counter
