Herfried,
"vbc /help" in .NET 2.0 beta 1 gives:
/platform:<string> Limit which platforms this code can run
on;
must be x86, x64, Itanium or anycpu
(default).
Which is what
http://blogs.msdn.com/joshwil/ suggested C# does.
Within VS.NET (beta 1) you can use "Project - Properties - Compile -
Advanced - Target CPU" to change the above setting.
Compiling the following with Target CPU = Itanium (Intel's 64-bit CPU):
Public Class MainForm
Public Shared Sub Main()
Dim index As Integer = 10
index *= 100
End Sub
End Class
Gives the following IL.
.method public static void Main() cil managed
{
.entrypoint
.custom instance void [mscorlib]System.STAThreadAttribute::.ctor() = ( 01
00 00 00 )
// Code size 11 (0xb)
.maxstack 2
.locals init ([0] int32 index)
.language '{3A12D0B8-C26C-11D0-B442-00A0244A1DD2}',
'{994B45C4-E6E9-11D2-903F-00C04FA302A1}',
'{00000000-0000-0000-0000-000000000000}'
// Source File 'C:\Documents and Settings\Jay\My Documents\Visual
Studio\Projects\Windows 64 Application\Windows 64 Application\MainForm.vb'
//000009: Public Shared Sub Main()
IL_0000: nop
//000010: Dim index As Integer = 10
IL_0001: ldc.i4.s 10
IL_0003: stloc.0
//000011: index *= 100
IL_0004: ldloc.0
IL_0005: ldc.i4.s 100
IL_0007: mul.ovf
IL_0008: stloc.0
//000012: End Sub
IL_0009: nop
IL_000a: ret
} // end of method MainForm::Main
Which demonstrates, as I was saying: VB.NET defines Integer as an alias for
Sytem.Int32.
Of course I need a Win64 machine to actually execute the above program
Note: The default of AnyCPU for Platform allows your single executable to
run as a 32-bit app on Win32 & a (full!) 64-bit app on Win64! Which IMHO
reinforces the notion that "Integer is an alias for System.Int32" even on
the 64-bit edition of .NET.
Of course if one really needs a platform specific Int, then one could use a
variation of Gerald earlier post.
Something like:
#If Is64BitSystem Then
Imports Int = System.Int64
#Else
Imports Int = System.Int32
#End If
Public Shared Sub Main()
Dim index As Int = 10
index *= 100
End Sub
Of course then you need to be careful of literals (100I verses 100L) and
public methods into & out of your assembly... (all the pain we learned from
C
)
Alternatively I would consider defining Int as a structure and overload all
the operators. Then compile 3 versions of the assembly with the Int
structure, one for each Target CPU. Which may introduce its own performance
issues, however like System.IntPtr I would only use Int for Interop...
I'm really not sure why there are 2 64-bit targets (x64 & Itanium). I would
expected only one...
Hope this helps
Jay
