Re: VB5 Long & Double to VB.NET

Armin,

Even Herfried is now advising to use the Int32 in API's.

I find it one of the stupidest decisions to let the Integer not to be the
same as the internal size of an accumulator. If that was than most programs
would benefit from the performance enhancements without rewriting,
rebuilding is than enough. However I thought it was the VB6 lobby which
forces us now to change all integers in Int64 and latter probably in Int128.

Cor

"Armin Zingler" <az.nospam@xxxxxxxxxx> schreef in bericht
news:ev6jA1uPHHA.4364@xxxxxxxxxxxxxxxxxxxxxxx
"Fabio Z" <znt.fabio@xxxxxxxxxxx> schrieb
"Terry" <news-grps@xxxxxxxxxxxxxxxxxxxxxxxx> ha scritto nel
messaggio

Thanks for the help. Long to int32 did the trick. As I am
calculating astrological positions I find that there are some
small differences between the Access VBA results and VB.NET for
the Sun and Moon of a couple of arc seconds each that I will need
to check out, apart from that all is working out just fine now.
It's great to finally get my first VB.NET solution working thanks.

I suggest to don't tie to language-specific data type.
Instead of ambiguos Integer (vb6/vb.net) or int (c#) for extern dll
calls use Int32 that tell you immediatly that you are working with a
32 bit integer.


Do you think, Integer will change in future again? Even if you target
Win64, Integer is still Int32. Just curious.


Armin


.