Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Marshall Conover <marzhall.o@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: segaloco <segaloco@protonmail.com>, 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 14:57:40 -0500	[thread overview]
Message-ID: <CAK0pxsEeY3dXkcvw8Zb=3brkGpwYNuYrWLMi1YwpuM2SEH9+Ew@mail.gmail.com> (raw)
In-Reply-To: <2CBA9AD7-BC25-40BF-ADE6-A6494D95A4B6@iitbombay.org>

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]

While all this error and exception discussion is going down, I have to
mention this piece: http://joeduffyblog.com/2016/02/07/the-error-model/

The author worked at MS on their "midori" research OS, and discussed what
went into their decisions around using return codes, exceptions, etc. I
felt it was a nice breakdown of the pros and cons of the different
approaches, and fleshed out the concepts in my mind a bit. I thought others
might enjoy it as well.

That said, I absolutely loathe exceptions with all my heart. In my
experience, along Warner and Matt's lines, they're more prone to the sort
of abuse that wastes my time than they are productive. It's not that they
can't be used well, they just so often aren't.

Cheers,

Marshall

On Fri, Mar 10, 2023 at 1:57 PM Bakul Shah <bakul@iitbombay.org> wrote:

> On Mar 10, 2023, at 10:03 AM, Dan Cross <crossd@gmail.com> wrote:
> >
> > On Fri, Mar 10, 2023 at 12:36 PM Bakul Shah <bakul@iitbombay.org> wrote:
> >> During development the runtime should simply invoke a debugger in this
> case. This should be perfectly doable but for some reason it is considered
> acceptable to crash a program! I don’t want to run a program *under a
> debugger* but want it invoked at the right time!
> >
> > Common Lisp implementations have been doing that for years! Too bad
> > using Lisp means bringing all the rest of the Lisp stuff with it,
> > including the attitude. Oh well. :-)
>
> It can even fix the problem and continue!
>
> Note that such things don't have to be *tied* to Lisp. But that
> would require a change in mindset.

[-- Attachment #2: Type: text/html, Size: 2254 bytes --]

  reply	other threads:[~2023-03-10 19:57 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 [this message]
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   ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
     [not found] <20230310121550.9A80718C080@mercury.lcs.mit.edu>
     [not found] ` <20230310131512.891A8212A8@orac.inputplus.co.uk>
2023-03-10 14:20   ` 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='CAK0pxsEeY3dXkcvw8Zb=3brkGpwYNuYrWLMi1YwpuM2SEH9+Ew@mail.gmail.com' \
    --to=marzhall.o@gmail.com \
    --cc=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).