Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: newlines in string constants
Message-ID: <9025@mimsy.UUCP>
Date: Sat, 17-Oct-87 15:56:46 EDT
Article-I.D.: mimsy.9025
Posted: Sat Oct 17 15:56:46 1987
Date-Received: Sun, 18-Oct-87 11:57:19 EDT
References: <2669@xanth.UUCP> <15262@clyde.ATT.COM> <2810@xanth.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 28

In article <2810@xanth.UUCP> kyle@xanth.UUCP (Kyle Jones), wanting
something like

>char *s = "This is
>not legal.";

to be declared legal, answers Forrest Gehrke:

>In article <15262@clyde.ATT.COM> feg@clyde.ATT.COM (Forrest Gehrke) writes:
>>How is the compiler going to divine the number (if any) of spaces you
>>will want?  The intervening spaces might have been intentional.

>Exactly.  I want the compiler to take everything that appears between
>the double quotes literally, with the exception of the usual backslash
>escapes.  My text editor knows how many spaces there are after "is", so
>the compiler certainly shouldn't have any problem grasping this.

Yep.  There are exactly 62 spaces there, of course.  What?  Did
you say you typed only one?  But surely you can see all the others
on that card.  Card?  Sorry, I should have said `card image'.

Oh, you are not using an IBM machine?

Remember that there *are* machines out there that work with fixed
length records, even for source code.  Some of them even have C compilers.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris