Peter,
If you want to move pixels fast, you need pointers. You also need to
eliminate bounds and error checking and code carefully so that they
are not needed. All the checking of these things that is intrinsic to
REALbasic is what I absolutely love about REALbasic. The speed
penalty is one I willingly pay. It makes developing software cheaper
and faster. Now, when I need speed, like for graphics operations, I
jump into plugin space. To me, this is a killer feature of the
REALbasic environment, not a problem.
Ever notice how rarely your REALbasic application will actually crash
while developing compared to say, an app written in C? That's doesn't
come for free.
-Brad
On Feb 15, 2006, at 2:02 PM, Peter K. Stys wrote:
Agree 100%, and it's unfortunate that we have to go to the extra
pains of writing plugins with Xcode et al. Which begs the
question, why is RB slower than C/C++? I'm not talking about GUI
widgets and event loops, but basic stuff. My image processing
involves very simple operations (add, mult, compare, access and
move pixels around enormous arrays) repeated zillions of times.
Why aren't such simple operations not compiled to the same fast
binaries as a C compiler?
With declares, there would be no need to use Xcode as we have
access to all the OS X calls. It's the speed issue only. But why?
P.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
