Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++ Subject: Re: How to write wide char string literals? Date: Thu, 01 Jul 2021 10:13:39 -0700 Organization: None to speak of Lines: 20 Message-ID: <871r8i9cu4.fsf@nosuchdomain.example.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: reader02.eternal-september.org; posting-host="f91b68b8a8f0fc876f265381b9366169"; logging-data="1941"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19V8jLbMj09n1eYz5H9CSI2" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:+Zy4Dd5rc4ZXhXfV6rihA2ENUl8= sha1:zVR4Tkcwkgsq3+39Rw92iqkK8uk= Xref: csiph.com comp.lang.c++:80607 Kli-Kla-Klawitter writes: > Am 01.07.2021 um 11:36 schrieb Ralf Goertz: >> Am Thu, 1 Jul 2021 11:10:55 +0200 >> schrieb Kli-Kla-Klawitter : [...] >>>> I know that. It's called a byte order mark. And gcc ignores it. >>> >>> No, wrong - gcc honors it since vesion 1.01. >> I created this file b.cc: [...] >> How does that qualify as “gcc honoring the BOM”? > > Use v1.01. You think you're funny. You're not. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Philips void Void(void) { Void(); } /* The recursive call of the void */