Yes, in most cases managed code will be measurably slower than doing about
the same thing in C++ (I've never used Delphi). However, it's hard to
provide a 100% "apples to apples" comparision because the CLR is doing so
much behind the scenes that you would have to do manually in C++ (or if you
prefer "the CLR adds a lot of overhead").
However, the thing with performance is to determine if it really matters in
a particular situation. The performace of managed code is adaquate for
large classes of applications. For those situations where there really is a
critical path of code that must squeeze out every last cycle from the CPU,
it's fairly straight forward for managed and unmanaged code to interoperate.
Finally, it is possible to construct very special cases where managed code
is actually faster than similar C++ code; this is because the JITter can
optimize to the exact hardware configuration.
The .NET APIs for AutoCAD are going to be more productive for most people
than using native ObjectARX, which means you can get working code faster.
For many people, this increase in productivity will outweigh any potential
performance concerns.
Dan
"Tony Tanzillo" wrote in message
news:4961263@discussion.autodesk.com...
Visual Studio.NET is not without its problems.
I've not stressed it anywhere near the point that I've
stressed the Delphi IDE (which also has problems, but
I've been able to develop fairly massive projects and
complete object frameworks with it).
For example, the Forms designer has bugs that cause
strange things to happen, like controls moving around
a form or container; TabPages that mysteriously and
randomly changing their order in a TabControl, are just
a few I've seen.
There are also some compiler bugs that can cause
the IDE to lock up when you build a project. That's
a good reason to build every time you change a few
lines of code, or introduce a new type, or anything
like that, so you know what caused it.
Managed code is also notoriously slow, or at least,
by C++ and Delphi standards (not sure aobut VB
since I've never used it much).
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
wrote in message news:4961065@discussion.autodesk.com...
Thank you for general view. But I need serious understanding of some points
of ObjectArx vs DotNet
1. execution speed
2. bugs in these tools
3. deployment
may be anybody have exactly view to these points.
Thank you