Option Strict Error on Const declaration.....

Option Strict Error on Const declaration.....

Post by Smith Gu » Sat, 28 May 2005 08:01:55


After declaring

Option Strict On

Iam getting the error on.

Private Const ERROR_SUCCESS = &H0

What is the correction needed for the above statement.

.Net Framework 1.1.

Thanks,

Smith
 
 
 

Option Strict Error on Const declaration.....

Post by Oenon » Sat, 28 May 2005 08:23:33


Private Const ERROR_SUCCESS As Integer = &H0

--

(O) e n o n e

 
 
 

Option Strict Error on Const declaration.....

Post by Ken Tucker » Sat, 28 May 2005 08:27:14

Hi,

Private Const ERROR_SUCCESS as integer = &H0

Ken
----------------


After declaring

Option Strict On

Iam getting the error on.

Private Const ERROR_SUCCESS = &H0

What is the correction needed for the above statement.

.Net Framework 1.1.

Thanks,

Smith
 
 
 

Option Strict Error on Const declaration.....

Post by Herfried K » Sat, 28 May 2005 09:02:10

"Smith Guy" < XXXX@XXXXX.COM > schrieb:

\\\
Private Const ERROR_SUCCESS As Int32 = &H0
///

--
M S Herfried K. Wagner
M V P <URL: http://www.yqcomputer.com/ ;
V B <URL: http://www.yqcomputer.com/ ;
 
 
 

Option Strict Error on Const declaration.....

Post by Phill. » Thu, 02 Jun 2005 22:20:49


Herfried,

Probably been asked before (apologies), but why do you favour
"Int32" over "Integer"? Is it just for clarity or are Our Friends in
Redmond planning to "upgrade" Integer to its 64-bit equivalent
any time soon?

TIA,
Phill W.
 
 
 

Option Strict Error on Const declaration.....

Post by Herfried K » Fri, 03 Jun 2005 02:48:10

"Phill. W" < XXXX@XXXXX.COM > schrieb:

I prefer to use the names of the types in the .NET Framework when dealing
with unmanaged code. It's only my personal preference.


'Integer' will remain 32-bit even in the 64-bit world.

--
M S Herfried K. Wagner
M V P <URL: http://www.yqcomputer.com/ ;
V B <URL: http://www.yqcomputer.com/ ;