Article View: comp.std.c
Article #5082Re: The \c escape
From: Patrick Powell
Date: Sat, 18 Jun 1988 15:49
Date: Sat, 18 Jun 1988 15:49
21 lines
1362 bytes
1362 bytes
In article <4604@haddock.ISC.COM> karl@haddock.isc.com (Karl Heuer) writes: >Add new escape sequence \c. > >Summary > >This proposal cleans up two warts in the language: initializing a character >array without adding a null character, and terminating a hexadecimal escape >which might be followed by a valid hexadecimal digit. It also allows the user >to explicitly document when a null character is unnecessary, e.g. >write(1,"\n\c",1). This is FAR too reasonable, clean, clear, simple, trivial to implement, does not break existing systems, etc., to even make it out the door. I think that you should aim for something more cryptic... difficult to word... you know, sort of "klugdy"... perhaps tied in with the preprocessor. And needing a keyword. Patrick Powell Prof. Patrick Powell, Dept. Computer Science, 136 Lind Hall, 207 Church St. SE, University of Minnesota, Minneapolis, MN 55455 (612)625-3543/625-4002
Technical Details
Message-ID:
<5907@umn-cs.cs.umn.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!husc6!uwvax!umn-d-ub!umn-cs!attila!papowellReferences:
<4604@haddock.ISC.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!husc6!uwvax!umn-d-ub!umn-cs!attila!papowell From: papowell@attila.uucp (Patrick Powell) Newsgroups: comp.std.c Subject: Re: The \c escape Message-ID: <5907@umn-cs.cs.umn.edu> Date: 18 Jun 88 15:49:31 GMT References: <4604@haddock.ISC.COM> Sender: news@umn-cs.cs.umn.edu Reply-To: papowell@attila.UUCP (Patrick Powell) Organization: University of Minnesota, Minneapolis Lines: 21