 |
C++Talk.NET
C++ language newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
blangela
Guest
|
 Posted: Thu Nov 16, 2006 4:10 am Post subject: VS .NET 2005 and forms |
 |
|
{ This seems to be marginally off-topic for [environment-specific];
let's try to stay on topic by not going into environment-specific
details but stating what's related to the standard C++ and what's not.
-mod }
If I want to take advantage of the "forms" capability of .NET 2005 and
I want to program in C++, am I required to use the "managed" C++ ? I am
referring to the same "forms" capability as is available to C#
programmers.
Also, can some one explain to me the difference between managed C++ and
regular C++ (ANSII compliant) ? Perhaps point me to a good link and/or
article on the web.
Thanks,
Bob
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ] |
|
| Back to top |
|
 |
Alf P. Steinbach
Guest
|
| Posted: Thu Nov 16, 2006 8:21 am Post subject: Re: VS .NET 2005 and forms |
|
|
* blangela:
| Quote: | { This seems to be marginally off-topic for [environment-specific];
let's try to stay on topic by not going into environment-specific
details but stating what's related to the standard C++ and what's not.
-mod }
If I want to take advantage of the "forms" capability of .NET 2005 and
I want to program in C++, am I required to use the "managed" C++ ?
|
No. Just about anything can be done in pure C++. It's a question of
practicality, though: by using a language specifically tailored to an
environment (and "managed" C++, as well as C++/CLI, are effectively
different different languages with about the same relationship to C++ as
C++ has to C) much is automated for you, and safety nets are in place.
However, instead of using a niche language like those two supersets of
C++ are, consider using a language dedicated -- not just tailored --
to the environment, for those tasks that are environment-specific.
Then use ordinary C++ for integration with more conventional
environments such as the OS API.
[snip]
| Quote: | Also, can some one explain to me the difference between managed C++ and
regular C++ (ANSII compliant) ? Perhaps point me to a good link and/or
article on the web.
|
<url: http://www.google.com/search?q=wikipedia+managed+c%2B%2B>.
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ] |
|
| Back to top |
|
|
Michael Olea
Guest
|
| Posted: Fri Nov 17, 2006 12:13 am Post subject: Re: VS .NET 2005 and forms |
|
|
Gerhard Menzl wrote:
| Quote: | Alf P. Steinbach wrote:
No. Just about anything can be done in pure C++. It's a question of
practicality, though: by using a language specifically tailored to an
environment (and "managed" C++, as well as C++/CLI, are effectively
different different languages with about the same relationship to C++
as C++ has to C) much is automated for you, and safety nets are in
place.
However, instead of using a niche language like those two supersets of
C++ are, consider using a language dedicated -- not just tailored
-- to the environment, for those tasks that are environment-specific.
Then use ordinary C++ for integration with more conventional
environments such as the OS API.
I don't think this is good advice. Easier integration of standard C++
code is one of the prime reasons to prefer C++/CLI over other .NET
languages.
|
There is an alternative: "Domain Specific Embedded Languages". See chapters
10 and 11 of "C++ Template Metaprogramming".
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ] |
|
| Back to top |
|
|
Alf P. Steinbach
Guest
|
| Posted: Fri Nov 17, 2006 10:10 am Post subject: Re: VS .NET 2005 and forms |
|
|
* Gerhard Menzl:
| Quote: | Alf P. Steinbach wrote:
No. Just about anything can be done in pure C++. It's a question of
practicality, though: by using a language specifically tailored to an
environment (and "managed" C++, as well as C++/CLI, are effectively
different different languages with about the same relationship to C++
as C++ has to C) much is automated for you, and safety nets are in
place.
However, instead of using a niche language like those two supersets of
C++ are, consider using a language dedicated -- not just tailored
-- to the environment, for those tasks that are environment-specific.
Then use ordinary C++ for integration with more conventional
environments such as the OS API.
I don't think this is good advice. Easier integration of standard C++
code is one of the prime reasons to prefer C++/CLI over other .NET
languages.
|
The time when development in just language, i.e. doing all (whatever the
task) in C++, is over, I think. In general. Using special purpose
variants of C++ in order to keep it all one language is probably futile.
But there may still be environments where one does not have a choice.
Anyway, for the concrete environment discussed here it's not difficult
to integrate existing traditional C++ code into new environment-specific
code written in environment-specific language(s).
It's easy to forget that C++ is designed for a specific class of
environments. But one wouldn't (normally) use some specially tweaked
variant of C++ to program for e.g. the Java virtual machine. Then why
should one do that for an almost identical other virtual machine?
It may make political sense (we've invested much in this new development
software from the vendor so we gotta use it all, and we don't want to
appear backwards not knowing much about what, according to the hype,
everybody else use), but IMHO it doesn't make much engineering sense.
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ] |
|
| Back to top |
|
|
Gerhard Menzl
Guest
|
| Posted: Fri Nov 17, 2006 10:10 am Post subject: Re: VS .NET 2005 and forms |
|
|
Michael Olea wrote:
| Quote: | I don't think this is good advice. Easier integration of standard C++
code is one of the prime reasons to prefer C++/CLI over other .NET
languages.
There is an alternative: "Domain Specific Embedded Languages". See
chapters 10 and 11 of "C++ Template Metaprogramming".
|
I don't have this book at my disposal, but I would be curious to learn
in what way template metaprogramming is relevant in this context. Could
you elaborate?
--
Gerhard Menzl
Non-spammers may respond to my email address, which is composed of my
full name, separated by a dot, followed by at, followed by "fwz",
followed by a dot, followed by "aero".
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ] |
|
| 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
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
