GNU bug report logs - #38237
I/O errors do not currently have their own exception type

Previous Next

Package: guile;

Reported by: Andy Wingo <wingo <at> pobox.com>

Date: Sat, 16 Nov 2019 21:11:01 UTC

Severity: normal

To reply to this bug, email your comments to 38237 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guile <at> gnu.org:
bug#38237; Package guile. (Sat, 16 Nov 2019 21:11:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to Andy Wingo <wingo <at> pobox.com>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Sat, 16 Nov 2019 21:11:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: bug-guile <at> gnu.org
Subject: I/O errors do not currently have their own exception type
Date: Sat, 16 Nov 2019 22:09:52 +0100

For R7RS, this should be true:

  (file-error? (guard (exn (else exn)) (open-input-file " no such file ")))

However currently an error during Guile's open-input-file doesn't raise
a specific-enough exception for file-error? to be implementable.
Something to fix.
This bug report was last modified 4 years and 159 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.