From 4434217314834470423
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,9a6b7da9ba54eaea
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 1993-07-09 11:24:18 PST
Path: gmd.de!xlink.net!howland.reston.ans.net!gatech!bloom-beacon.mit.edu!eru.mt.luth.se!lunic!sunic!uts!iesd!news.iesd.auc.dk!abraham
From: abraham@research.att.com (Per Abrahamsen)
Newsgroups: comp.std.c++
Subject: Re: C++ Language Extensions
Message-ID: <ABRAHAM.93Jul9193316@loke.iesd.auc.dk>
Date: 9 Jul 93 17:33:16 GMT
References: <25936@alice.att.com> <SCHOUTEN.93Jul5141810@sp95.csrd.uiuc.edu>
	<25939@alice.att.com> <21cgc4$l1@senator-bedfellow.MIT.EDU>
	<25957@alice.att.com> <GEIR.HALBO.93Jul8234702@villtind.ugle.unit.no>
	<25978@alice.att.com>
Sender: news@iesd.auc.dk (UseNet News)
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 19
In-Reply-To: ark@alice.att.com's message of 9 Jul 93 09:54:32 GMT
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: GNUS 3.15
Mime-Version: 1.0


>>>>> "Andrew" == Andrew Koenig <ark@alice.UUCP> writes:

Andrew> The C committee is doing the same thing for C; with a little luck the
Andrew> two sets will be compatible :-)

This seems unlikely given

Andrew> Thus if it makes sense to use (< and >) as equivalents for {
Andrew> and } (which I think is what the [ C++ ] committee agreed to do),
Andrew> there is no way a macro can accomplish that.

and

Andrew> [ ... ] even though the C committee is going with the
Andrew> macro approach.

It seems like we will and up with two incompatible solutions to a
problem many ISO 646 users would prefer to see unresolved.