From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: read errors
Date: Tue, 6 Aug 2002 01:15:56 +0200 [thread overview]
Message-ID: <15695.1836.222887.354220@blauw.xs4all.nl> (raw)
In-Reply-To: <ljhei9fakv.fsf@burns.dt.e-technik.uni-dortmund.de>
marius.vollmer@uni-dortmund.de writes:
> > Maybe this is a kludge?
>
> No, I think it's the best we can do with the present system.
ok.
> > snprintf (s, 1024, "%s\nThis happened in %s%s%s line %d column %d", message,
>
> Can we use scm_simple_format here? That would avoid the 1024 limit
> and would also feel more gentle since we don't need to poke into the
> strings private parts.
Yep, done, committed. (Scheme beginner, didn't know about
simple-format.)
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-05 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 23:21 read errors Han-Wen Nienhuys
2002-08-05 18:02 ` Marius Vollmer
2002-08-05 18:16 ` Han-Wen Nienhuys
2002-08-08 17:50 ` Marius Vollmer
2002-08-05 23:15 ` Han-Wen Nienhuys [this message]
2002-08-06 12:02 ` Marius Vollmer
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=15695.1836.222887.354220@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@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).