From LAUER@yalph2.physics.yale.edu Wed Apr 1 03:26:13 1995 Received: from yalph1.physics.yale.edu by dkuug.dk with SMTP id AA24902 (5.65c8/IDA-1.4.4j for ); Wed, 29 Mar 1995 14:23:45 +0200 Received: from yalph2.physics.yale.edu by yalph2.physics.yale.edu (PMDF V4.3-7 #8220) id <01HOP7JB3KLS9OCUJV@yalph2.physics.yale.edu>; Wed, 29 Mar 1995 07:26:13 EDT Date: Wed, 29 Mar 1995 07:26:13 -0400 (EDT) From: LAUER@yalph2.physics.yale.edu Subject: c preprossor for conditional compilation To: SC22WG5@dkuug.dk Reply-To: LAUER@yalph2.physics.yale.edu Message-Id: <01HOP7JB4IIQ9OCUJV@yalph2.physics.yale.edu> X-Vms-To: IN%"SC22WG5@dkuug.dk" Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT X-Charset: ASCII X-Char-Esc: 29 Hi, I agree with Jamie that using the c preprossesor is a good idea. However, my experience leaves me in doubt whether it is viable. In particular when using the c preprossesor for fortran code on the Alpha AXP running open VMS I had a rude shock... all spaces where converted to a single space I called DEC and was informed that the C standard defines this behaviour for the preprocessor. Clearly this will not work for fortran (the first 7 spaces get converted to one space. A line like character* 10 myvar gets converted to character* 10 myvar Does anyone know for sure what the current C standard says about the behaviour of the preprocessor regarding multiple spaces ? Rochelle Lauer Yale University High Energy Physics