From 8640373966200669757 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,dfce3f6ed7b423cd X-Google-Attributes: gidf78e5,public From: Al Stevens Subject: Re: maturity of the STL as a standard in the C++ standard library Date: 1998/06/17 Message-ID: #1/1 X-Deja-AN: 363671956 Approved: stephen.clamage@sun.com (comp.std.c++) References: <6m2afs$9e2$1@nnrp1.dejanews.com> <6m6g1q$439$1@nnrp1.dejanews.com> NNTP-Posting-Date: Wed, 17 Jun 1998 16:18:15 CDT Originator: clamage@taumet X-NNTP-Posting-Host: 199.233.112.82 X-UID: 0000000001 X-Status: $$$T X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: Newscene Public Access Usenet News Service (http://www.newscene.com/) Newsgroups: comp.std.c++ >I've never used MFC, so I really can't comment here. Generally, I would >avoid MFC like the plague, if only for portability reasons. (I've also >heard nothing but bad about it... Then you are practicing selective listening. :-) There has lots of good said about MFC, particularly when it is being compared to its competition. Portability? If you are looking for cross-GUI solutions, then you are stuck with developing applications that offer the lowest common denominator of user interface features. If you want to exploit all the latest Win32 and ActiveX features (and want to use a C++ framework), MFC used to be your only real choice because the others are usually behind Microsoft in new feature support. I'm not familiar with the ILog Views library you mention, though, and perhaps there is another choice. Who publishes ILog Views? [ 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://reality.sgi.com/austern_mti/std-c++/faq.html ]