Re: The future of C++
From: Thomas Richter (thor_at_cleopatra.math.tu-berlin.de)
Date: 04/20/04
- Next message: Hyman Rosen: "Re: C++ and Middleware"
- Previous message: christopher diggins: "Re: Feasability of Design By Contract (DBC) approach in standard C++"
- In reply to: David Eng: "The future of C++"
- Next in thread: David Eng: "Re: The future of C++"
- Reply: David Eng: "Re: The future of C++"
- Reply: Jim Melton: "Re: The future of C++"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 20 Apr 2004 14:28:47 +0000 (UTC)
Hi,
> As I posted in CORBA group, I believe the future of C++ depends on
> CORBA (the same is true that the future of CORBA depends on the future
> of C++). Applications are built today are distributed applications
> instead of stand alone applications. For C++ to success in this
> environment, it has to have a middleware platform. C++ has a
> disadvantage comparing to Java and C# which both have a middleware
> platform. However, CORBA can become the middleware platform for C++.
Oh well. For that to happen, the OMG should possibly do its homework
first. I'm using CORBA with its C++ bindings here, and I'd to read the
"standard literature" for that task, the Henning/Vinoski book, and the
C++ CORBA bindings are *still* giving me headaches. Does it really
have to be *that* complicated? I wouldn't have problems with two
mappings, or a layered design with a simple, general purpose
top-layer, and a specialized layer that provides all the fancy
extensions I rarely need. Currently, CORBA and its C++ mapping is both
too special and too general at once.
I also feel that CORBA does its job possibly only half the way it could.
For example, it nicely runs new threads for me serving my objects, but
at the same time it doesn't provide necessary services for keeping
object states consistent amongst the threads - there are no "mutex"
specifications in CORBA.
On the plus side, CORBA provides lots of language bindings, so I can
really interact with Java, Python, Perl,..., but the integration into
the C++ language really deserves a cleanup.
> The answer is clear, the C++ standard committee and OMG
> must work together to create a better mapping and association between
> C++ and CORBA.
Bingo.
So long,
Thomas
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]
[ comp.std.c++ is moderated. To submit articles, try just posting with ]
[ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
[ --- Please see the FAQ before posting. --- ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html ]
- Next message: Hyman Rosen: "Re: C++ and Middleware"
- Previous message: christopher diggins: "Re: Feasability of Design By Contract (DBC) approach in standard C++"
- In reply to: David Eng: "The future of C++"
- Next in thread: David Eng: "Re: The future of C++"
- Reply: David Eng: "Re: The future of C++"
- Reply: Jim Melton: "Re: The future of C++"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|