John Nagle <firstname.lastname@example.org> wrote:
JN > How about a strongly typed C++ interface for Photon? The
JN > code output by PhAB will compile with C++. We compile
JN > everything with C++ and it works fine. So this could
JN > be done without modifying PhAB. Just give us C++ people
JN > a typesafe interface file to include.
JN > John Nagle
JN > Team Overbot
I second the motion.
This reminds me of an old story from way out in left field.
Ages ago, Borland’s Phillie Kahn (sp?) came out with their first C++
compiler. Phillie made a statement that C++ was undoubtedly the way to
program for the future and that all Borland products from then on would
be written in C++.
Round about the same time Billy Gates also made a public statement,
something to the effect that C++ was just another of the latest software
fads and that Microsoft wasn’t going to bother to persue it.
About 5 years later Microsoft decided that all of their future software
projects would be written in C++.
Somewhere around 12 years ago Dan Dodge made a statement that C++ was
just too inefficient for the QSSL to bother spending any development
efforts in C++.
Even so, I’d put any application written using the Watcom C++ compiler
up against the same application written for and compiled by the GNU C
I think it would be prudent for QSSL to realize that C++ is here to stay
and that customers, including their big automotive customers, are in
fact using it. C++ has already stood the test of time.
Also, QSSL needs to do somethnig about getting a real commercial compiler
for QNX. Once upon a time the QNX OS would blow the doors off of a
similar application written for MicroSlob even if the MS version were
running on a computer that was twice as fast. Now it is only a little
faster when run in the same environment.
Congradulations! QSSL wanted to catch up to Microsoft.
Well, your almost there.