Why is this code not compiled
Const
UnsignedValue As UInteger = &H80004005To make it more strange this compiles:
Const
UnsignedValue As Integer = &H80004005The value is larger than Integer.MaxValue but smaller than UInteger.MaxValue.
Handling of unsigned values?
Hot Topic
- Really simple question!!
- COM hellp
- Making a simple calculator in VB
- Best way to make frequently used functions available to all apps?
- How can I share the Main Module between projects?
- Accessing Online Books
- Using WebBrowser Control: ComboBox & CheckBox
- Form1_closing.. is this a bug?
- Attempting to add a datasource
- Looping varibles
Visual Basic
- Catch user mouse click events in window.
- Process Lock Up
- Searching files for specific strings/text
- Multiple forms / vb 2005
- Missing start page?
- WSE, Datasets, help needed asap!
- REQUEST: IDE Support for AddHandler
- how to send commands to a mdiparent from an mdichild
- Launch VB Program Instead of Default Browser
- How do I execute a sub in different form?
Handling of unsigned values?
shunm_ms
Thank you for this information.
IngJVV
Samuel D. Colak
In VB, literals (including hexadecimal literals) are considered to have type integer - as such &H80004005 is actually a negative number (representation in two's complement) - so in your first statement you're trying to assign a negative integer to an unsigned variable, and in the second statement you're assigning a valid negative number to an integer variable.
Use &H80004005UI to specify that the variable is mean as an unsigned type