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
Message-Id:	<199909242135.QAA25831@mercury.xraylith.wisc.edu>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: can I use STL in src/winsup ?
In-Reply-To:	Your message of "Fri, 24 Sep 1999 15:58:38 EDT."
	<199909241958 DOT PAA31691 AT envy DOT delorie DOT com>
Date:	Fri, 24 Sep 1999 16:35:29 -0500
From:	Mumit Khan <khan AT thor DOT xraylith DOT wisc DOT edu>

DJ Delorie <dj AT delorie DOT com> writes:
> 
> 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.

We should not add any more dependencies in winsup, especially libstdc++,
which is going through a major change (libstdc++-v3). One example of 
breakage is when STL allocators were in the past, it caused binary 
incompatibility, and that's highly undesirable. Take this scenario for
example: I build cygwin.dll using my version of the compiler which 
uses a different version of SGI STL, and you build your yours using a
different version. Now the two are incompatible!  No good, sorry.

We should also stay far away from cutting edge C++ features in winsup,
and features that can have adverse performance ramifications.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -