Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Fri, 24 Sep 1999 15:58:38 -0400 Message-Id: <199909241958.PAA31691@envy.delorie.com> From: DJ Delorie To: stmax@pigeonpoint.com CC: cygwin@sourceware.cygnus.com In-reply-to: <37EBD225.2F9E7FC3@pigeonpoint.com> (message from Stas Maximov on Fri, 24 Sep 1999 12:33:57 -0700) Subject: Re: can I use STL in src/winsup ? References: <37EBD225.2F9E7FC3@pigeonpoint.com> > I have looked through src/winsup. Nobody uses STL there. Is it a special > agreement not to use STL there? Can I start using it? Please don't. We've had cases in the past of STL changing out from under us (in subtle ways) and breaking winsup builds. I'd prefer if you stuck to code local to cygwin and well-defined ansi/posix function calls. Also, adding STL means that STL has to be built as part of the winsup snapshots, and it currently isn't. We'd have to add all of STL (and possibly other C++ libraries) to the snapshot builds and sources if you use it. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com