From: Lars Brinkhoff <lars@nocrew.org>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Conditions, AKA exceptions.
Date: Fri, 10 Mar 2023 13:09:25 +0000 [thread overview]
Message-ID: <7wwn3o21oa.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20230310121550.9A80718C080@mercury.lcs.mit.edu> (Noel Chiappa's message of "Fri, 10 Mar 2023 07:15:50 -0500 (EST)")
Noel Chiappa writes:
> I was just astonished that in a long thread about handling exceptional
> conditions, nobody had mentioned . . . exceptions. Clearly, either
> unfamiliarity (perhaps because not many laguages provide them - as you
> point out, Go does not), or not top of mind.
Seems to me exceptions are quite mainstream: CLU, C++, Java, C#,
JavaScript, Python all have them. Arguably Go too, in the form of
panic/recover.
next prev parent reply other threads:[~2023-03-10 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 12:15 [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Noel Chiappa
2023-03-10 13:09 ` Lars Brinkhoff [this message]
2023-03-10 17:15 ` [TUHS] Re: Conditions, AKA exceptions Paul Winalski
2023-03-10 13:15 ` [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Ralph Corderoy
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=7wwn3o21oa.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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).