Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++ Subject: Re: C++ variable names Date: Thu, 16 Jan 2020 00:15:09 -0800 Organization: None to speak of Lines: 42 Message-ID: <878sm7hl6a.fsf@nosuchdomain.example.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="71ac4e0bc340f3cd3245a2ba0fe88e42"; logging-data="13303"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Hq0m0OQnUdtceZ3fNpHss" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cancel-Lock: sha1:bL7adH6txiRorOFqxnJCsEZQTsI= sha1:1XienNRWl9ZK7ouAeAa/3zf5pg8= Xref: csiph.com comp.lang.c++:71410 T writes: [...] > This got it? > > C C++ > float_t std::float_t > double_t std::double_t float_t and double_t are fairly obscure types defined in in C, and in or in C++. float_t is at least as wide as float, and might be wider and faster; similarly for double_t. (For example, float_t might be defined as double if double operations are faster than float operations.) See the C standard (I think you have N1570) section 7.12. I don't know that there would be any reason to refer to them in Raku. The predefined floating-point types in both C and C++ are float, double, and long double. I'm really not sure what this whole discussion is about. The types in the standard library have names defined by the standard library as specified in the language standard. You just use those names. It doesn't make sense to talk about changing them. If you weren't aware, most of the C standard library headers are incorporated into the C++ standard library. Each C header is available in C++ as , with the declarations in the std:: namespace. With very few exceptions, they're the same. Any decent C++ reference should explain all this. No offense, but I get the feeling that you have some fundamental misconception that led you to think that, for example, referring to int32_t as int32 might make some kind of sense. Hopefully this means you won't have to post a new question about size_t and ptrdiff_t, since the answers will be exactly the same. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com [Note updated email address] Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */