Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Octal Date: Mon, 02 Jan 2017 12:35:24 -0800 Organization: None to speak of Lines: 22 Message-ID: References: <9f751874-98cf-4208-b809-9e6424600ac6@googlegroups.com> <5de6cdd0-6a36-40da-9bd6-4387d43c7947@googlegroups.com> <9cb7833a-8479-4e61-8398-690783c4d975@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="16a71c89bad48345b6871a676d7f8d6a"; logging-data="11404"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18t92yqQiobD4/xYhnJzdiU" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:6fwVgDU11Z0SEUjLGq1JFAdIpF0= sha1:WZAi2qN5cpQQJRJuTcPdMVCgKXo= Xref: csiph.com comp.lang.c:100902 Tim Rentsch writes: > Keith Thompson writes: [...] >> I believe the description of the preprocessing phases is specifically >> designed to permit a conforming compiler to use text as the output of >> the preprocessor. > > Sort of. I think that is true for the _ultimate_ output > of the preprocessor, but not for intermediate outputs, > which have to preserve token boundaries without adding > extra spaces to do so (because of how stringizing has > to work). What I referred to as "the output of the preprocessor" was the output of translation phase 5. (Phase 6 concatenates string literals; I'm assuming that's not done by the preprocessor, though it could be.) -- 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"