With reference to the C++ test (benchmark_03.htm), the results you got ARE
what I would have expected. 3 months ago, I wouldn't have said that was the
case, but then someone told me about the concept of 'cache misses' and 'page
faults'. It all apparently relates to the fact that there are not just 2
areas of memory on a computer as many people think (hard disk, slow access
but massive space, and RAM, fast access but small space). There is actually
a third - processor cache (very fast access but tiny space). Apparently the
more localized variables are, the more likely they are to be stored in the
processor cache when needed again. This makes the C++-style of code you have
in example 2 more localized, because the loop is actually a declarative
region of its own, in which some variables are defined which means the
compiler knows they won't be used outside of that area.
(Apparently! :-) )
"Marchel" <ma*****@comcast.net> wrote in message
news:m8********************@comcast.com...
For a long time I was a gib fan of Borland C++ Builder with VCL framework
and never gave a second look in Microsoft products since I've seen MFC. Anyway, recently Borland decided out of the
blue to abandon it's C++ Builder and I decided to give a look into the .NET C++ and .NET C# products. After briefly
playing with them I put them to test against each other in some floating point tasks. The outcome might surprise you. It
certainly surprised me !
See for yourself:
http://mywebpages.comcast.net/marche...nchmark_01.htm
JM
