From: David Pirotte <david@altosw.be>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 29684@debbugs.gnu.org
Subject: bug#29684: exception printers - request for improvement
Date: Sun, 1 Jul 2018 19:23:21 -0300 [thread overview]
Message-ID: <20180701192321.75afe2e1@capac> (raw)
In-Reply-To: <87in5yrk9z.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]
Hello Ludovic,
> ...
> It seems to me that you can achieve similar effect, at least in some
> cases, by parameterizing ‘current-error-port’. It also makes more sense
> to me to parameterize ‘current-error-port’ rather than set
> ‘exception-format’, because the ‘exception-format’ is very constrained:
> it has to implement at least everything ‘simple-format’ implements.
>
> WDYT?
>
> Besides, note that there’s also ‘set-exception-printer!’. It’s a
> different kind of customization, but it can serve a similar purpose.
To be honest, exactly how does not really matter, I leave that to you (maintainers):
I have used the code, actually written by Daniel, who also claimed it was not
complete, iirc, to raise the issue, so we can discuss it between us:
I think we should be very (very) friendly to new Guile users, and especially
those who do not know scheme (yet);
I think I should be able to use Guile-CV to teach basic image manipulation
to a class of young teenagers, who would not even know what scheme is, which
means, imo, no guile customization should be required:
guile
(use-modules (cv))
(im-load "my-preferred-penguin.png")
- at this point, even if the image is very small, guile is 'lost' [*]
- same if I teach them to compose a few image ops, they commit
a mistake while typing .. bang, the exception printer is 'lost'
It is perfectly fine, on the opposite side, to ask advanced scheme users (who would
want to, but I really don't see the point) configure guile s the repl and the
exception printer so it tries to print the full content of huge lsts, vectors, arrays
...
David
[*] one could argue i could have chosen another data structure, but well, I
did not :), and imo, we can't tell users who have to manipulate large
structures (arrays, vector, think about non s/w engineers scientists,
biologists ...), "... don't manipulate large structures in a repl, wrap them
in a record first ..."
it happened to me at university, trying to make a demo of Guile-CV to a group
of postdoc candidates: I updated guile the day before and forgot to repatch
both the repl and the exception printers, opened an image, and ... bang!
I was in emacs, so ... after a few seconds they all laughed and ... by
the time I could recover, repatched guile ... they were all ...
gone! (and convinced they should stick to python and open-cv or java and
imagej ...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-01 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 3:26 bug#29684: exception printers - request for improvement David Pirotte
2018-07-01 16:30 ` Ludovic Courtès
2018-07-01 22:23 ` David Pirotte [this message]
2018-07-02 6:49 ` Ludovic Courtès
2018-07-03 19:31 ` David Pirotte
2018-07-04 9:30 ` tomas
2018-08-04 2:17 ` David Pirotte
[not found] <mailman.20.1513184404.6520.bug-guile@gnu.org>
2017-12-14 14:38 ` Daniel Llorens
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=20180701192321.75afe2e1@capac \
--to=david@altosw.be \
--cc=29684@debbugs.gnu.org \
--cc=ludo@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).