I know this isn't necessary any more - but here's an VB example of that declaration crap...
Create a CommandButton and parse this code into its Click-Event:
Dim a As Integer
Dim b, c As Integer
a = 1.95583
b = 1.95583
c = 1.95583
MsgBox CStr(a) + vbCrLf + CStr(b) + vbCrLf + CStr(c)
Let's take a look at it...
We have declared 3 Variables ... it should be 3 Integers (well, they aren't - at least one of them)
Now we give a floating point number to these Vars.
B'cause Variable a and c
are 'real' Integers, the floating point value is rounded to 2. But in Var b, which is Variant Type, VB stores the number as a floating point number - that's not what we wanted, right?
dgp9999 and SaiNt:
As for the method of declaring - I think it would *really* be better if Microsucks wouldn't have implemented that damn Variant Type - it's completely useless and just annoys programmers
- Alhexx