Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!ulysses!hector!jss
From: jss@hector.UUCP (Jerry Schwarz)
Newsgroups: comp.lang.c
Subject: Re: Macro parameters getting substituted into strings
Message-ID: <10221@ulysses.homer.nj.att.com>
Date: 10 Apr 88 20:11:02 GMT
References: <11879@brl-adm.ARPA> <4099@hoptoad.uucp> <7309@brl-smoke.ARPA> <7566@brl-smoke.ARPA> <1039@mcgill-vision.UUCP>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: jss@hector (Jerry Schwarz)
Organization: AT&T Bell Labs, Murray Hill
Lines: 17

In article <1039@mcgill-vision.UUCP> mouse@mcgill-vision.UUCP writes:
>
>Then we are faced with a loss of functionality.  Suddenly there is no
>way to define _IO or CTRL that is compatible with existing usage.  It
>is reasonable to require us to rewrite our macro definitions; it is not
>reasonable to require us to rewrite all our uses of the macro.  

Its been several months since I made my comment: "the standard does
not break programs, new compilers break programs".   It seems
releveant here. If there is a loss of functionality it is because a
compiler vendor who provided this functionality in the past is
failing to provide it now.  If you want a portable program you can't
use this functionality, but that is not a change since in the past not
all compilers provided it.

Jerry Schwarz
Bell Labs, Murray Hill