Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: // comments and \ Date: Wed, 02 Dec 2015 14:22:08 -0800 Organization: None to speak of Lines: 23 Message-ID: References: <46229a54-c99c-4682-9536-387bdff39d88@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="25540"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Pn4n9EtZHFu1epX4xmKA7" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:5ft9E4e+VXf9JsFbebtJIT8GinE= sha1:DAyfMW1DZb7eEWtIt2gXVLtcIYE= Xref: csiph.com comp.lang.c:77675 Nobody writes: > On Wed, 02 Dec 2015 07:08:28 -0800, supercat wrote: >> I still fail to see the need for such things to be part of the language >> specification. > > Well, they don't strictly *need* to be part of the language specification, > but putting them there avoids the situation where everyone rolls their own > solution. > > I'll just point out that platform-specific issues relating to text files > were enough of a problem for enough people that digraphs made it into C99 > and trigraphs have survived a number of attempts at removing them > (although it appears that they will become an implementation-dependent > option in C++17). Trigraphs were introduced in ANSI C89. Digraphs were added by the 1995 amendment. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"