Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com From: "Gary R. Van Sickle" To: "Cygwin-Apps" Subject: RE: libgetopt++ and setup and libstdc++ Date: Sat, 27 Apr 2002 21:43:14 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > Ok, > we're finally there. Setup now can use libstdc++ routines, > allowing the full range of C++ programming constructs. Probably even > exceptions, but I have not tested that yet. > As the late Kool-Aid man once said, "OH YEAH!"! [snip] > We can also use the C++ string class. However, except for the trivial - > such as option parsing - we should still use the cistring or String++ > classes, as we need unicode support eventually, and also formatmessage > support. They can of course use string as an underlying container if > appropriate. > There's a cute 'trick' here that gives you the best of both worlds: typedef basic_string< TCHAR > StringAW; Now the "StringAW" type is either wide or narrow depending on build-time defines. -- Gary R. Van Sickle Brewer. Patriot.