Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++ Subject: Re: To C or not to C++ Date: Wed, 17 Aug 2022 14:49:35 -0700 Organization: None to speak of Lines: 24 Message-ID: <87zgg2bkwg.fsf@nosuchdomain.example.com> References: <2868500762@darkrealms.ca> <87iln0owgr.fsf@nosuchdomain.example.com> <87h72cc67o.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: reader01.eternal-september.org; posting-host="f86eb84281c805881a6d37bf9a5499bc"; logging-data="593567"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+v2u//B3g1kDWfWIFQEX2F" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:aNeGPbXdfIaJeaNiYMLMitxdr0A= sha1:5pRbZGSxXk7mhefgmeYsomZKGWo= Xref: csiph.com comp.lang.c++:85967 Muttley@dastardlyhq.com writes: > On Tue, 16 Aug 2022 12:56:59 -0700 > Keith Thompson wrote: >>You're right, it's not correct to say that `char *str = "hello";` "won't >>compile as C++". A conforming compiler must diagnose it, but after > > Thank you. We got there in the end. > >>I'd say the content of the warning was relevant. You chose to omit it >>for some reason. > > The assertion was it wouldn't compile, not that it would compile with warnings. > > For an activity such as programming that requires attention to detail a lot of > you here are rather lacking in that ability. You could have helped by providing just a little extra information. You chose not to. Consider trying to be helpful rather than just showing off your ability to be obscure. -- 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 */