From: "N.M. Maclaren" <nmm1@cam.ac.uk>
To: Fortran List <fortran@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, libfortran] Thread safety and simplification of error printing
Date: Mon, 09 May 2011 04:00:00 -0000 [thread overview]
Message-ID: <Prayer.1.3.3.1105082349450.13601@hermes-2.csi.cam.ac.uk> (raw)
In-Reply-To: <BANLkTi=iW_tg46dp8z8JnHd=PnKsVrrOcg@mail.gmail.com>
On May 8 2011, Janne Blomqvist wrote:
>>
>> It's theoretically insoluble, given the constraints you are working
>> under. Sorry. It is possible to do reasonably well, but there will
>> always be likely scenarios where all you can do is to say "Aargh!
>> I give up."
>
>Well, I realize perfection is impossible, so I'm settling for merely
>improving the status quo!
Very reasonable, given the problem. Where the effort increases rapidly
with the reliability, not being too fancy is a sound strategy.
>I think in our case the situation is a bit easier in that we're not
>trying to recover from a serious failure, merely print some diagnostic
>information without getting stuck in a deadlock.
I wasn't trying to do much more! I was mainly trying to maximise the
chances of files being closed cleanly and appropriate diagnostics
being produced. Once there was a serious error, I didn't allow the
program to continue. But I did allow user-written exception handlers
(which could only return - NOT jump out). Even that was hard enough :-(
Regards,
Nick Maclaren.
next prev parent reply other threads:[~2011-05-08 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 17:07 Janne Blomqvist
2011-05-08 13:44 ` Janne Blomqvist
2011-05-08 17:35 ` N.M. Maclaren
2011-05-08 22:50 ` N.M. Maclaren
2011-05-09 2:31 ` Janne Blomqvist
2011-05-09 4:00 ` N.M. Maclaren [this message]
2011-05-08 23:01 ` Janne Blomqvist
2011-05-13 11:00 ` Janne Blomqvist
2011-05-14 10:26 ` Steve Kargl
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=Prayer.1.3.3.1105082349450.13601@hermes-2.csi.cam.ac.uk \
--to=nmm1@cam.ac.uk \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).