From: ori@eigenstate.org
To: covertusername967@gmail.com, 9front@9front.org
Subject: Re: [9front] libmp and error handling
Date: Wed, 21 Oct 2020 06:53:23 -0700 [thread overview]
Message-ID: <1795470027CF8F4349F3EB3E6D25A7EF@eigenstate.org> (raw)
In-Reply-To: <B85822567C216B2353517698C32250DB@gmail.com>
> This is a better idea. Even better, just leave the other programs as
> is and make sysfatal a default. Thanks!
This is still likely to require quite a bit of change in libmp; if
it's currently calling sysfatal, then it's very likely full of
things like:
x = a();
y = b()
return mpadd(x, y);
which means that if b() errors, then x is leaked.
next prev parent reply other threads:[~2020-10-21 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 3:56 covertusername967
2020-10-21 4:08 ` Alex Musolino
2020-10-21 4:27 ` covertusername967
2020-10-21 13:53 ` ori [this message]
2020-10-24 23:52 ` covertusername967
2020-10-25 0:25 ` ori
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=1795470027CF8F4349F3EB3E6D25A7EF@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=covertusername967@gmail.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).