From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: gethost error display
Date: Thu, 01 Jul 2004 10:40:11 +1000 [thread overview]
Message-ID: <87y8m48sr8.fsf@zip.com.au> (raw)
In-Reply-To: 87llifzj3u.fsf@trouble.defaultvalue.org
Rob Browning <rlb@defaultvalue.org> writes:
>
> The scm_error call in
> scm_resolv_error passes the bad host name as a format argument, but
> none of the error messages have format escapes.
Yep, they're just the hstrerror strings.
> so that we pass the bad hostname as one of the exception extra data
> items rather than making it the first format string item.
Or alternately, perhaps just quietly drop it. Other system errors
don't include the offending filename or whatever in the throw.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-07-01 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 21:38 gethost error display Kevin Ryde
2004-06-22 15:51 ` Rob Browning
2004-07-01 0:40 ` Kevin Ryde [this message]
2004-08-12 1:05 ` Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y8m48sr8.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).