Using Uint in VB .NET

[Howard Kaikow]

C# allows one to specify a constant with a type of uint, so you could have,
say:

private const uint varname = 0xFFFFFFF0

How does one port such statements to VB .NET?

--
http://www.standards.com/; See Howard Kaikow's web site.

[Herfried K. Wagner [MVP]]

"Howard Kaikow" <ka****@standards.com> schrieb:

C# allows one to specify a constant with a type of uint, so you could
have,
say:

private const uint varname = 0xFFFFFFF0

How does one port such statements to VB .NET?

Currently that's not supported by VB.NET because VB.NET doesn't "natively"
support unsigned types (notice that the unsigned types are not CLS
compliant).

Untested:

\\\
Private ReadOnly varname As UInt32 = _
Convert.ToUInt32(&HFFFFFFF0)
///

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Howard Kaikow]

I had tried something like that.

Error returned is "Value was either too large or too small for a UInt32."

The only things that "work" are

Private ReadOnly varname As Integer = &HFFFFFFF0
Const zz As Integer = &HFFFFFFF0

--
http://www.standards.com/; See Howard Kaikow's web site.
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:eH**************@tk2msftngp13.phx.gbl...

"Howard Kaikow" <ka****@standards.com> schrieb:

C# allows one to specify a constant with a type of uint, so you could
have,
say:

private const uint varname = 0xFFFFFFF0

How does one port such statements to VB .NET?

Currently that's not supported by VB.NET because VB.NET doesn't "natively"
support unsigned types (notice that the unsigned types are not CLS
compliant).

Untested:

\\\
Private ReadOnly varname As UInt32 = _
Convert.ToUInt32(&HFFFFFFF0)
///

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Gerald Hernandez]

Even if you get any of these variations to actually compile, it is still of
little use.
While VB.Net (pre 2005) does allow you to declare Unsigned Ints, there are
no operators.
You can add, subtract, etc. not even within the same data type.
Even simple compares will choke in many cases.

Gerald

[Gerald Hernandez]

that should read...
You can "NOT" add, subtract, etc...

"Gerald Hernandez" <Cablewizard@sp*********@Yahoo.com> wrote in message
news:uq**************@tk2msftngp13.phx.gbl...

Even if you get any of these variations to actually compile, it is still of little use.
While VB.Net (pre 2005) does allow you to declare Unsigned Ints, there are
no operators.
You can add, subtract, etc. not even within the same data type.
Even simple compares will choke in many cases.

Gerald

[Howard Kaikow]

"Gerald Hernandez" <Cablewizard@sp*********@Yahoo.com> wrote in message
news:uq**************@tk2msftngp13.phx.gbl...

Even if you get any of these variations to actually compile, it is still of little use.
While VB.Net (pre 2005) does allow you to declare Unsigned Ints, there are
no operators.
You can add, subtract, etc. not even within the same data type.
Even simple compares will choke in many cases.

I understood that.

Fer now, I'm just passing a constant to a sub/function, so I can get by
cheating with Integer.

[Gerald Hernandez]

"Howard Kaikow" <ka****@standards.com> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...

"Gerald Hernandez" <Cablewizard@sp*********@Yahoo.com> wrote in message
news:uq**************@tk2msftngp13.phx.gbl...

Even if you get any of these variations to actually compile, it is still

of

little use.
While VB.Net (pre 2005) does allow you to declare Unsigned Ints, there are no operators.
You can add, subtract, etc. not even within the same data type.
Even simple compares will choke in many cases.

I understood that.

Fer now, I'm just passing a constant to a sub/function, so I can get by
cheating with Integer.

As long as you resign yourself to using bit-wise operations only, then this
is your best bet. It is what I do, and it works quite well. If you need that
extra top bit, then the best thing to do is work with a Long (Int64).
Sometimes that extra bit is all you really need, it seems a shame to waste
another 32. But hopefully this will be solved with VB 2005.

Gerald