Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.glorb.com!news-out.readnews.com!transit3.readnews.com!s09-10.readnews.com!not-for-mail From: Patrick Scheible Newsgroups: comp.lang.c Subject: Re: trigraphs, yecch References: <4f2808f4.648026530@text.giganews.com> <86aa53e59d.fsf@zipcon.net> <17a0be0b-94ca-4d18-a8f0-f5f073c623f4@v14g2000vbc.googlegroups.com> Date: Mon, 06 Feb 2012 20:40:27 -0800 Message-ID: <86mx8vmf2c.fsf@zipcon.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (berkeley-unix) Cancel-Lock: sha1:2CP0gdKfl9yReS5ePYwQt0HWzR4= MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Lines: 15 Organization: The Zip Connection (zipcon.net) NNTP-Posting-Host: 48534cbb.news.zipcon.net X-Trace: DXC=D9YN^^92:;VkW3GH]N8K\VU>Dm5d6:E6]>I?lnAl3ECP^FZK]QK0XnY_A>1gcoFWo]n[lCEiQbYl_ X-Complaints-To: abuse@zipcon.net Xref: x330-a1.tempe.blueboxinc.net comp.lang.c:16814 "christian.bau" writes: > On Feb 1, 5:50 am, "Charles Richmond" wrote: > >> So just *remove* trigraphs from the *next* C standard.  Or require the >> preprocessor symbol "__TRIGRAPH_IMPLEMENTED__" to be defined, or relegate >> this to a PRAGMA...  before trigraphs would be recognized by the compiler. >> Make it *extra* hard for the ordinary C programmer to step on this land >> mine. > > A change that would silently break existing code. How much existing code uses trigraphs? -- Patrick