Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <v2rbg7$2i5ih$3@dont-email.me>
Deutsch   English   Français   Italiano  
<v2rbg7$2i5ih$3@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.c
Subject: Re: C23 thoughts and opinions - why so conservative?
Date: Sat, 25 May 2024 00:31:03 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <v2rbg7$2i5ih$3@dont-email.me>
References: <v2l828$18v7f$1@dont-email.me>
	<20240523171911.00002f5a@yahoo.com> <v2o7re$1tlge$1@dont-email.me>
	<20240524003424.0000590a@yahoo.com> <v2op72$2017t$3@dont-email.me>
	<v2p94a$26km6$1@dont-email.me> <v2p9cg$26gfp$4@dont-email.me>
	<v2pd6k$278q5$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 25 May 2024 02:31:04 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="8b960b0d1c1f0cbc9fa414c8762c1a10";
	logging-data="2692689"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19I4GIWpxiuK8bpg5Fut42I"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:4Mvjp1Z1Ktzo2RWA3tYAQ1VLxB0=
Bytes: 2058

On Fri, 24 May 2024 07:47:48 +0100, Malcolm McLean wrote:

> I virtually always use goto for memory allocation failure.
> 
> It does mean that, strictly, the function is no longer a "structured"
> subroutine. But reality is usually that memory allocation failure will
> mean program termination pretty soon.

Hmm, there may be a point in that. Consider also that Linux systems are 
typically configured to overcommit memory allocations: they never say 
“no”, but when they start running low, then they start killing the big 
memory hogs.

However, there are other dynamic checks that may need to be done. For 
example, trying to load an image, and discovering that your decoder cannot 
handle it, possibly because it is corrupted or the wrong format 
altogether. It would be nice to recover gracefully from this sort of 
situation. And not have the decoder crash or leak memory.