Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <000a01c14c75$ae9eeca0$01000001@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
References: <04b201c14c73$12b6bb80$01000001 AT lifelesswks> <20011003212901 DOT B5900 AT redhat DOT com> <000201c14c74$92b705f0$01000001 AT lifelesswks> <20011003213636 DOT C5900 AT redhat DOT com>
Subject: Re: C++ templates and cygwin?
Date: Thu, 4 Oct 2001 11:41:17 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
> >do you mean the STL, or handling of templates?  I'd have thought that
> >older g++'s were irrelevant as cygwin is built with a patched gcc
> >anyway - can that not be set as a minimum requirement?
>
> Both, actually.  I thought that there were problems with templates in
> general and STL in particular.  Or maybe incompatibilities is a better
> way of describing the problem.

I'm not sure. I don't think gcc had a full STL until quite recently -
but as I've never used the STL I'm guessing :].

> Now, I'm wondering if there were code size issues too.  Is it
possible
> that using STL will pull in lots of extra unneeded cruft?

The STL is not an issue for me - it's the template capability. I'm more
than happy to roll a new iterator without the STL - if the STL is the
issue.

I don't believe that using the STL per se generates cruft though - it's
quite highly optimised code in there.

Rob