Path: csiph.com!news.mixmin.net!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c++
Subject: Re: recovering from std::bad_alloc in std::string reserve
Date: Mon, 31 May 2021 14:44:50 -0700
Organization: None to speak of
Lines: 14
Message-ID: <87r1hmy3vx.fsf@nosuchdomain.example.com>
References: <s8hkt2$liv$1@dont-email.me> <s8lt9d$tf0$1@dont-email.me> <s8m48i$g6f$3@dont-email.me> <s8nbvd$5ah$1@dont-email.me> <s8oqn6$fbj$1@dont-email.me> <_CUrI.452334$ST2.205157@fx47.iad> <87sg27zu0i.fsf@nosuchdomain.example.com> <87o8cvzsux.fsf@nosuchdomain.example.com> <s8p9ak$gun$1@dont-email.me> <87k0njzq45.fsf@nosuchdomain.example.com> <664dd958-6042-4d5d-951c-191b0e26421dn@googlegroups.com> <87fsy7zhxd.fsf@nosuchdomain.example.com> <2b396397-2ee8-4900-8969-8e59162f4c20n@googlegroups.com> <87bl8uzncv.fsf@nosuchdomain.example.com> <s8t2jn$ll2$1@dont-email.me> <ebbd50a2-ddbb-4344-9450-d2b77967621dn@googlegroups.com> <s92001$iei$1@dont-email.me> <87v96yy3yr.fsf@nosuchdomain.example.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="76c895cdea9def4cb68984464fb003ed"; logging-data="28262"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18IUaK0yJE/6EtnpfgBHc1K"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Cancel-Lock: sha1:CL/VVqNBaSA2huNi058WHbO3llI= sha1:8BuPLbGWSvCBDNwXwvW+WZ5nd2g=
Xref: csiph.com comp.lang.c++:80029

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
[...]
> Perhaps some future version of C might have enough capabilities to
> allow defining a longest integer type without causing ABI issues
> the way intmax_t did.

And I did it again.  s/C/C++/, or s/comp.lang.c++/comp.lang.c/.

[...]

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */