Article <20240328122327.3895243496305c8cc8a9d063@g{oogle}mail.com>

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 <20240328122327.3895243496305c8cc8a9d063@g{oogle}mail.com>

Deutsch English Français Italiano

<20240328122327.3895243496305c8cc8a9d063@g{oogle}mail.com>

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

Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Anton Shepelev <anton.txt@g{oogle}mail.com>
Newsgroups: comp.lang.c
Subject: Re: A Famous Security Bug
Date: Thu, 28 Mar 2024 12:23:27 +0300
Organization: A noiseless patient Spider
Lines: 34
Message-ID: <20240328122327.3895243496305c8cc8a9d063@g{oogle}mail.com>
References: <bug-20240320191736@ram.dialup.fu-berlin.de>
	<20240320114218.151@kylheku.com>
	<20240321211306.779b21d126e122556c34a346@gmail.moc>
	<20240321131621.321@kylheku.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 28 Mar 2024 09:23:31 +0100 (CET)
Injection-Info: dont-email.me; posting-host="b2af8e000113f14e0de58c4b02eef262";
	logging-data="3673424"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/6lgA4cq6T/wjC+Upwitv3L0wYot1K37g="
Cancel-Lock: sha1:lV2kqi8vbgmvQ8pftTA6PGqGqBA=
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Bytes: 2236

Kaz Kylheku:

> If C compilers warned about every piece of dead code that
> is eliminated, you'd be up to your ears in diagnostics all
> day.

Is so much dead code a defect in the source or a benigh
consequence of a well-pondered decision?

> If you do want the code deleted, that doesn't always mean
> you can do it yoruself. What gets eliminated can be target
> dependent:
>
>   switch (sizeof (long)) {
>   case 4: ...
>   case 8: ..
>   }

The case above is IMHO best handled by conditional
compilation, even though more work may be required to
dispatch on a type size in the preprocessor.

> Because memset is part of the C language, the compiler
> knows exactly what effect it has (that it's equivalent to
> setting all the bytes to zero, like a sequence of
> assignments).

Yes, it is an instance of a special case relying upon hard-
coded information.  Why not, however, let the programmer
elimitate this dead code from his code, if it /is/ dead?

-- 
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments