 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Randall Parker Guest
|
Posted: Thu Feb 02, 2006 5:18 am Post subject: My C++ versus V++/CLI questions |
|
|
I asked these in another thread but suspect they were missed since the thread has
gotten so long:
I'm trying to get some sense of how far apart C++ and C++/CLI are going to grow.
Will anything from C++/CLI get added to regular C++ in order to help maintain
portability between the languages? Are there even features in C++/CLI that seem
appealing and acceptable to people on the ISO C++ committee?
Can many things from C++/CLI get added to regular C++ without having the CLI/CLR
stuff as the target? How much of C++/CLI could get implemented (at least in theory)
by compiler that produces native code?
Also, how many of the likely to be accepted proposals for the next ISO C++ rev be
incompatible with C++/CLI and simply be unable to be ported to C++/CLI?
Also, if one is willing to sacrifice the ability to allow one's C++ classes to be
usable from, say, C# are there any additional things one can do with C++/CLI to
compile more real ISO C++ compliant source code?
|
|
| Back to top |
|
 |
Edward Diener Guest
|
Posted: Thu Feb 02, 2006 1:48 pm Post subject: Re: My C++ versus V++/CLI questions |
|
|
Randall Parker wrote:
| Quote: | I asked these in another thread but suspect they were missed since the
thread has gotten so long:
I'm trying to get some sense of how far apart C++ and C++/CLI are going
to grow.
Will anything from C++/CLI get added to regular C++ in order to help
maintain portability between the languages? Are there even features in
C++/CLI that seem appealing and acceptable to people on the ISO C++
committee?
Can many things from C++/CLI get added to regular C++ without having the
CLI/CLR stuff as the target? How much of C++/CLI could get implemented
(at least in theory) by compiler that produces native code?
Also, how many of the likely to be accepted proposals for the next ISO
C++ rev be incompatible with C++/CLI and simply be unable to be ported
to C++/CLI?
Also, if one is willing to sacrifice the ability to allow one's C++
classes to be usable from, say, C# are there any additional things one
can do with C++/CLI to compile more real ISO C++ compliant source code?
|
You need to ask questions about the future of C++/CLI to Microsoft. The
place for that is probably microsoft.public.vc.language or
microsoft.public.dotnet.languages.vc.
You need to ask about the future of the C++ standard to the C++ standard
commitee. The best place to ask about that is comp.std.c++.
While you can ask on Borland's NGs, the answers you will get are
probably going to be conjecture unless a representative from Microsoft
who is knowledgable about their future plans for C++/CLI or a member of
the C++ standard committee answers you. But I think you are making a bad
assumption that members of the C++ standard commitee are going to be
driven by a need to conform to C++/CLI.
|
|
| Back to top |
|
 |
Chris Uzdavinis (TeamB) Guest
|
Posted: Thu Feb 02, 2006 4:02 pm Post subject: Re: My C++ versus V++/CLI questions |
|
|
Randall Parker <STOPtechiepundit (AT) EVILfuturePOXpunditSPAM (DOT) com> writes:
| Quote: | Will anything from C++/CLI get added to regular C++ in order to help
maintain portability between the languages? Are there even features in
C++/CLI that seem appealing and acceptable to people on the ISO C++
committee?
|
I think so. Alistair and I wrote a proposal for adding virtual
functions with explicit 'override' semantics to get compile-time
checking that what you think overrides something actually does. (And
a "new" virtual function actually doesn't override an existing one.)
It's slightly different semantics from the C++/CLI but still anything
is better than nothing.
| Quote: | Can many things from C++/CLI get added to regular C++ without having
the CLI/CLR stuff as the target? How much of C++/CLI could get
implemented (at least in theory) by compiler that produces native code?
|
I guess our proposal fits here. But "can" and "will" are vastly
different. The C++ committee has to think hard about every change
they make, and won't do anything lightly. There are oftentimes
surprises that even the most apparently harmless change can have.
--
Chris (TeamB);
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|