From: Andy Wingo <wingo@pobox.com>
To: Zefram <zefram@fysh.org>
Cc: 16357@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#16357: insufficient print abbreviation in error messages
Date: Tue, 21 Jun 2016 17:10:13 +0200 [thread overview]
Message-ID: <871t3qy3vu.fsf__9403.4242596992$1466521897$gmane$org@pobox.com> (raw)
In-Reply-To: <20160621123840.GZ1170@fysh.org> (zefram@fysh.org's message of "Tue, 21 Jun 2016 13:38:40 +0100")
On Tue 21 Jun 2016 14:38, Zefram <zefram@fysh.org> writes:
> Andy Wingo wrote:
>>Thoughts?
>
> How was this managed in Guile 1.8?
The printers and the backtrace handling was quite different, but it used
"print states".
> It seems that you need the truncated-print mechanism to be always
> available internally, but this doesn't require that it be always visible
> to the user. You can still require the full libraries to be loaded for
> the user to get access.
>
> Lazy loading sounds like a bad idea. Error handling is a bad place to
> attempt something that complex and failure-prone.
That's what we do for backtrace printing in 2.2, for what it's worth.
It's a tradeoff between memory size, good errors, maintainability,
startup time, safety, duplication... the global optimimum corresponds to
no per-axis optimimum :/
Andy
next prev parent reply other threads:[~2016-06-21 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:00 bug#16357: insufficient print abbreviation in error messages Zefram
2016-06-21 12:17 ` Andy Wingo
2016-06-21 12:38 ` Zefram
2016-06-21 15:10 ` Andy Wingo [this message]
2016-06-23 16:57 ` Mark H Weaver
[not found] ` <87lh1vrggi.fsf@netris.org>
2016-06-23 17:59 ` Andy Wingo
2016-06-26 1:05 ` Mark H Weaver
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='871t3qy3vu.fsf__9403.4242596992$1466521897$gmane$org@pobox.com' \
--to=wingo@pobox.com \
--cc=16357@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=zefram@fysh.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).