Hello,

since value types don't have to be dereferenced, they're supposed to be
faster than reference types (exceptions aside). To prove this, I developed a
testprg in VB and to my surprise and the opposite proofed! I looked at the
IML-Code and noticed, that the VB-compiler "invented" an other (third) value
type object, even if I only used two value types in the sample. I then did
the same in C#, and the IML-code was perfect.

So my questions are:

a) Does anybody know about a "weird" behaviour with value types of the
vb.compiler?
b) (Has nothing to do with this, just another question): Can I assume that a
value type is usually to be accessed quicker, since the probability that it
is already hosted in a processor cache is higher than with referece types
(at least if a program cosumes large amount of space)?

If you want to have the samples for testing, simply mail me to
testaccount01 at loeffelmann dot de

Klaus