From: Paul Winalski <paul.winalski@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: coff@tuhs.org
Subject: [COFF] Re: Conditions, AKA exceptions.
Date: Mon, 13 Mar 2023 13:10:17 -0400 [thread overview]
Message-ID: <CABH=_VSLp52gB1+kszMBe3BgxZ+PM2kJwrQgp-z2fBwzAVNosA@mail.gmail.com> (raw)
In-Reply-To: <20230313164718.4169E21F37@orac.inputplus.co.uk>
On 3/13/23, Ralph Corderoy <ralph@inputplus.co.uk> wrote:
>
>> That said, I absolutely loathe exceptions with all my heart.
>
> I'm not a fan either.
Exceptions play merry hell with compiler optimizations. If you are in
a piece of code where an exception can occur, unless you have
knowledge of the global side-effects of the handler(s) that might get
invoked you must abandon any attempts to do data flow analysis of
global data items.
The C++ Standard Library is fond of using throw and catch exception
handling. An optimizing compiler pretty much has to throw all data
flow optimization involving global variables, or things passed to a
callee by pointer, if anything in the call chain calls a C++ Standard
Library routine.
From a compiler writer's perspective, the name STD for the C++
Standard Library is most apt. STD routines are a disease that infects
anything that touches them.
-Paul W.
next prev parent reply other threads:[~2023-03-13 17:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:11 [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
2023-03-10 17:28 ` segaloco via COFF
2023-03-10 17:34 ` Larry McVoy
2023-03-10 17:35 ` Bakul Shah
2023-03-10 17:42 ` Larry McVoy
2023-03-11 11:28 ` [COFF] Conditions, AKA exceptions Ralph Corderoy
2023-03-12 4:23 ` [COFF] " Theodore Ts'o
2023-03-12 10:44 ` Ralph Corderoy
2023-03-12 16:46 ` Paul Winalski
2023-03-12 16:53 ` Larry McVoy
2023-03-10 17:43 ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) segaloco via COFF
2023-03-10 18:03 ` Dan Cross
2023-03-10 18:57 ` Bakul Shah
2023-03-10 19:57 ` Marshall Conover
2023-03-13 16:47 ` [COFF] Conditions, AKA exceptions Ralph Corderoy
2023-03-13 17:10 ` Paul Winalski [this message]
2023-03-13 21:12 ` [COFF] " Dave Horsfall
2023-03-10 17:47 ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABH=_VSLp52gB1+kszMBe3BgxZ+PM2kJwrQgp-z2fBwzAVNosA@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=coff@tuhs.org \
--cc=ralph@inputplus.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).