Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!adm!dsill@NSWC-OAS.arpa
From: dsill@NSWC-OAS.arpa (Dave Sill)
Newsgroups: comp.lang.c
Subject: Re: Null-terminated C strings
Message-ID: <11332@brl-adm.ARPA>
Date: 19 Jan 88 20:27:23 GMT
Sender: news@brl-adm.ARPA
Lines: 19

In article <2294@haddock.ISC.COM> Karl Heuer <karl@haddock.ISC.COM> writes:
>|"The \c escape at the end of a string literal suppresses the trailing NUL.
>|If it appears other than at the end, it is ignored, but may serve to separate
>|an octal or hex escape from a following digit."  [Proposed wording]
>
>So, what do y'all think?  Is this a good idea?  Should the two features both
>exist but have different notations?  (That was my original plan, with "\c" to
>suppress the NUL and "\z" to represent a zero-width separator.)

I like \c for suppressing the trailing *null character* (NUL implies
ASCII), but I don't think a zero-width separator is needed because the
automatic concatenation of adjacent string literals added by X3J11 can
perform the same function.

=========
The opinions expressed above are mine.

"I shed, therefore, I am."
					-- ALF