Board index » cppbuilder » Re: C++\CLI compiler

2007-09-11 11:06:42 PM
cppbuilder11
Daniel James wrote:
experience. The only time I have used managed C++ was to wrap a plain C
library (graphviz) so I could call it from a C# app. Even though
microsoft cleaned up managed C++ in .net 2.0, it is still a messy beast.
Certainly not as clean as C# or native C++. So, I only use it when I
have no other legitimate choice.
I am glad that managed C++ exists, but it is never going to be the first
tool that I pull out of the toolbox.
help.
H^2
 

geikelite wrote:
Windows Presentation Foundation. WPF is too young to adopt at this
point. Designer support is lacking, and I'm not sure I want huge parts
of my application coded in xml. Compile time type checking is a good thing.
If you must use microsoft technologies to create a client application,
windows forms is the easily best library to choose. Your other choices are
- WPF (not ready for primetime)
- MFC (a shining example of everything you shouldn't do)
- WTL (little known C++ library that I don't think is supported)
- VB6 (you too can be an average developer)
- straight win32 (its 1992 all over again)
Windows forms is a lot like the VCL. Say what you want about microsoft,
but one thing they have mastered is the art of stealing good ideas.
H^2
 

good though.
 

{smallsort}

Hendrik Schober wrote:
pretty large project in MFC, before I knew other RAD frameworks. You can
develop with it, but IMHO VCL and the other RAD frameworks are more
straightforward.
possible, but it's a pain in the a...
because a customer has raised a question what Vista has to offer for
native development, besides all that many new managed API's.
customer base. Many stated just the opposite.
But you mentioned the main reason why C++ compatibility isn't touched
(besides that C++ is an ISO standard) - Windows itself is written in
C/C++ ;-).
 

"Leo Siefert" < XXXX@XXXXX.COM >wrote
folks who are interested in .NET to plan.
I'm showing below a quote from Steve Teixeira on the MS VC++ team that has
bearing on this thread. It is taken from a comment (Sept. 07) from the
following msdn blog by Somasegar on August 08:
blogs.msdn.com/somasegar/archive/2007/08/08/visual-c-futures.aspx
Here is the comment from Steve Teixeira. Some straightforward talk, slightly
out of context.
"The recommendation we're making here is that if you're going to make a
technology decision to build a user interface using one of the managed UI
frameworks, you need to invest in building C# and/or VB.NET expertise on
your development staff. I've yet to talk to a customer for whom this is a
serious problem, but I admit I haven't talked personally to all of them. :)
The bigger picture here is that leaving this space in the capable hands of
C# and VB.NET gives us the ability organizationally to focus on the native
UI space (which I fully admit we haven't done a good job at in recent
versions). I fully expect that we're going to take some heat for stating our
intentions and recommendations in this space so bluntly, but I believe it's
the right thing to do because it enables customers to plan their technology
investments accordingly ."
 

Frank J wrote:
warranted.
 

"Alex Bakaev [TeamB]" < XXXX@XXXXX.COM >wrote in message
VCL is more productive, but it runs slower.
There is always that scale of productivity...production vs. performance.
 

Frank J wrote:
--
Rudy Velthuis [TeamB]
"DOS Computers manufactured by companies such as IBM, Compaq,
Tandy, and millions of others are by far the most popular, with
about 70 million machines in use worldwide. Macintosh fans, on
the other hand, may note that{*word*19}roaches are far more numerous
than humans, and that numbers alone do not denote a higher life
form." -- New York Times, November 26, 1991
 

"Frank J" < XXXX@XXXXX.COM >wrote in message>
but one thing that has always seemed real good about the VCL was it's
windowing performance with even very complicated forms. It seems to be very
'optimized'.
Perhaps you were testing a specific feature that isn't?
The only thing that bugs me performance-wise is this very {*word*193} flicker I
get on my iMac when resizing tab pages.
 

"Rudy Velthuis [TeamB]" < XXXX@XXXXX.COM >wrote in message
longer.
You know I'm saying in comparison to MFC...but I done dealing with you.
 

"Harold Howe [TeamB]" < XXXX@XXXXX.COM >wrote in message
COM.
But, this is where C++/CLI helps out greatly.
 

Frank J wrote:
test parameters were? I'm curious how does one derive a test for a UI
framework?
thanks,
.a
 

"Alex Bakaev [TeamB]" < XXXX@XXXXX.COM >wrote in message
.NET is slower than the VCL.
 

Alex Bakaev [TeamB] wrote:
TThread, TDataset, AnsiString etc.
--
frode
 

Harold Howe [TeamB] < XXXX@XXXXX.COM >wrote:
(My only excuse is that you fooled others, too.)
--
XXXX@XXXXX.COM is never read
I'm HSchober at gmx dot de
"A patched buffer overflow doesn't mean that there's one less way attackers
can get into your system; it means that your design process was so lousy
that it permitted buffer overflows, and there are probably thousands more
lurking in your code."
Bruce Schneier