Return-Path: <jpierce@nyc.rr.com>
Mailing-List: contact xerces-c-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list xerces-c-dev@xml.apache.org
Received: (qmail 22799 invoked from network); 4 Feb 2001 14:52:42 -0000
Received: from nycsmtp1fb.rdc-nyc.rr.com (HELO nyc.rr.com) (24.29.99.76)
  by h31.sny.collab.net with SMTP; 4 Feb 2001 14:52:42 -0000
Received: (apparently) from jungle1 ([24.168.138.170]) by nyc.rr.com  with
 Microsoft SMTPSVC(5.5.1877.357.35);
	 Sun, 4 Feb 2001 09:54:00 -0500
Message-ID: <000c01c08eba$163cf9d0$aa8aa818@jungle1>
From: "Jonathan Pierce" <jpierce@nyc.rr.com>
To: <xerces-c-dev@xml.apache.org>
References: <Pine.LNX.4.10.10102041001190.27716-100000@rksystems.com>
Subject: Re: Bugs and Compile Problems in 1.4.0
Date: Sun, 4 Feb 2001 09:52:23 -0500
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
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

> Not much point in replacing <iostream.h> with <iostream> if you're going
> to drag the entire std namespace back in.  The whole point of <iostream>
> is to provide safer/more precise control over which names were assumed
> to come from the std namespace.
>

I realize that it has equivalent meaning.
The issue was whether to allow or require this syntax at all in common
files.
The argument against it is that some platforms might not support it yet so
those platforms won't be able to compile the common files if the style is
used.

Jonathan