Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 24 Sep 1999 15:58:38 -0400
Message-Id: <199909241958.PAA31691@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: stmax AT pigeonpoint DOT com
CC: cygwin AT sourceware DOT cygnus DOT 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 DOT 2F9E7FC3 AT pigeonpoint DOT 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 AT sourceware DOT cygnus DOT com