Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: segaloco <segaloco@protonmail.com>
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary)
Date: Fri, 10 Mar 2023 09:47:29 -0800	[thread overview]
Message-ID: <1DCF3FAD-ADAA-4FEC-8A76-739DF67A4859@iitbombay.org> (raw)
In-Reply-To: <zQ8vnI_R8uVwIaiBNo8FIH-OWMoES4VHfnxnnCNISkbFkJcpenXi4H75Z7zFStfclQAue8mixqjL6rWIMBAYRi3bbeGdv0SQUHA9NbQAb44=@protonmail.com>

I should add that (compared to goto or setjmp/longjmp), by making exceptions a language thing, the compiler can attach more context to the exception event (or condition). In the scheme I outlined, the vendor library function must declare what exceptions it doesn’t handle and the compiler can pass more context that may not make sense to a library user but may help its developer pinpoint the cause.

> On Mar 10, 2023, at 9:28 AM, segaloco <segaloco@protonmail.com> wrote:
> 
> If nothing else, I could provide much better stack traces to vendors when I'm particularly stuck on something and convinced it isn't my fault. Maybe such a thing exists in C# but I've never gone looking for it, all I know is catching an exception from some vendor library with zero useful information makes me want to take a hammer to much more than the code...

  parent reply	other threads:[~2023-03-10 17:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 17:11 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             ` [COFF] " Paul Winalski
2023-03-13 21:12               ` Dave Horsfall
2023-03-10 17:47   ` Bakul Shah [this message]
     [not found] <20230310121550.9A80718C080@mercury.lcs.mit.edu>
     [not found] ` <20230310131512.891A8212A8@orac.inputplus.co.uk>
2023-03-10 14:20   ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Larry Stewart
2023-03-10 18:09     ` Steffen Nurpmeso
2023-03-10 17:34   ` Warner Losh

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=1DCF3FAD-ADAA-4FEC-8A76-739DF67A4859@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=coff@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).