Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ames!think!paperboy!meissner From: meissner@osf.org (Michael Meissner) Newsgroups: comp.lang.c Subject: Re: How can I de-escape my strings at run time? Message-ID: Date: 3 Jun 90 19:41:00 GMT References: <6550.26639B0A@puddle.fidonet.org> <2596@litchi.bbn.com> <896@wraith.cs.uow.edu.au> <:9W3JZ3@ggpc2.ferranti.com> Sender: news@OSF.ORG Organization: Open Software Foundation Lines: 18 In-reply-to: peter@ficc.ferranti.com's message of 3 Jun 90 13:43:43 GMT In article <:9W3JZ3@ggpc2.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes: | I'm mildly surprised X3.159 doesn't include \e for escape, since they | added \xNN \a and so on... was it considered? It came up a few times. The problem is that ANSI C is not mandated to require ASCII (or even ISO646). EBCDIC is the classic counterpoint. Some of the people in the committee also observed that is was kind of silly to specify something, which is always used in a non-portable fashion (ie, terminal/printer control strings), when there was always \nnn around to do exactly the same thing, in the same non-portable manner. -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA Catproof is an oxymoron, Childproof is nearly so