Re: Upgrading to VB.Net

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Armin Zingler wrote:
An Integer in VB6 is 16 bits while the "native integer" (machine word)
is 32 bits. How do you mean that the Integer type is a "pseudo code"
for the "native integer"?

Yes, now it's 32 bits, but VB6' Integer has been inherited from previous versions when it was a native integer on 16 bit machines.

No, it never was a native integer.

I'm not talking about documented, platform specific types like we have with IntPtr now. I mean, it has not been documented anywhere that "Integer is the platform specific integer type", but it was the type commonly used for integer operations and it "happened to" match the native integer size.

That's my point, it once was picked to be the same size as the current machine word, but it has never been depending on the actual size of the machine word.

And I agree that this is not true
anymore (that's the "confusing" part).

As it was never true, how is it confusing that it's not true now? ;)

I think it was true.

If it was once true, it would be true now also, which it clearly isn't.

Besides, if it's not confusing with a 16 bit Integer on a 32 bit platform, how can it be confusing with a 32 bit Integer on a 64 bit platform?

Anyway, who actually cares? ;-)

Well, I care because I don't want too much misinformation floating around. Cor clearly stated that an Integer is 16 bits on a 16 bit platform and 32 bits on a 32 bit platform, and that is a connection that doesn't exist at all. He also said that VB6 produces 16 bit software, which it never has.

--
Göran Andersson
_____
http://www.guffa.com
.

Relevant Pages

  • Re: Moving from C++ to VC++
    ... > have been bad to constrain fseek to 16 bit int offsets, so they used long, ... > for a standard type like long, ... general-purpose integer type on the platform. ...
    (microsoft.public.vc.language)
  • Re: Delay Routine: Fully-portable C89 if possible
    ... integer type that has exactly 32 value representational bits. ... A platform that has no such type can't run that code as designed, so there's no point for it to compile on that platform. ... 32-bit integers - it's not clear whether you are trying to say that the cpu in question must be at least 32 bits (which is of course not the case - your code would work perfectly well on an 8-bit cpu, which regularly have 16-bit hardware registers and perhaps also 32-bit hardware registers) or just that it can work with 32-bit data. ...
    (comp.arch.embedded)
  • Re: Delay Routine: Fully-portable C89 if possible
    ... integer type that has exactly 32 value representational bits. ... A platform that has no such type can't run that code as designed, so there's no point for it to compile on that platform. ... One of them is that it's quite hard to implement its functionality unless you're the compiler implementor. ...
    (comp.arch.embedded)
  • Re: Upgrading to VB.Net
    ... The way you do it by removing words in sentences other people wrote, you can make from every sentence the oposite by instance by simply removing a word as "not" ... Armin does natively not speak the same language as I. (I don't know what your native language is, but I have the idea that it's like English in the Germanic language space, like Armins and my native language) ... I mean, it has not been documented anywhere that "Integer is the platform specific integer type", but it was the type commonly used for integer operations and it "happened to" match the native integer size. ... Besides, if it's not confusing with a 16 bit Integer on a 32 bit platform, how can it be confusing with a 32 bit Integer on a 64 bit platform? ...
    (microsoft.public.dotnet.languages.vb)
  • Interface Vs Xml....Discussion
    ... Now I am confusing About ... Should I Release XML Tags...(My New Language Based on XML Format) ... --Implementor can DEVELOP PLATFORM on their OWN WAY ... --End User(Business Logic Developer) Can SWITCH Between Multiple ...
    (comp.object)