From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: guile 3 update, halloween edition
Date: Thu, 31 Oct 2019 11:46:53 -0300 [thread overview]
Message-ID: <20191031114653.3854ebcb@capac> (raw)
In-Reply-To: <87o8xyhtz6.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
Hello Andy,
> ...
> Thoughts welcome! Also: should these structured error objects be
> named exceptions or conditions? SRFI-35, R6RS, and R7RS say
> "conditions", but racket and my heart say "exceptions"; wdyt?
I personally prefer "exceptions" over "conditions", though I did read
and understand Chris answer ...
Now, slightly of topic, but since/while you are working on (ice-9
boot), exceptions ... please allow me this gentle ping and invite you
to (re)read my answer to the following 'bug report' (1), which is a
'claim' in favor of, in 3.0, to have the repl, errors and backtraces
printers to truncate by default, then, to make things so that it would
be 'dead easy' to toggle those to full print 'on demand' ... up to one
could then bind the toggle proc(s) to an FN key ...
(1) https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36677#23
To 'quote myself':
Imo, no matter how easy it would be/is to change, the default
should be to enable truncated printing for the repl, erros and
backtraces, then indeed we should have 'dead easy' 'toggle'
mechanism for those 'extremely rare' guilers/situations
who/that requires/want (occasionally in my experience, I
sometimes do to of course) full print ...
I was recently reading an email (or was it on irc, I don't remember)
fom Rekado, who wrote guile-studio, which is great news, and an attempt
make guile's newbie first experience(s) quite a lot more
friendly ...
With the above claim (and a 'dead easy' toggle mechanism ...), I would
feel quite a lot more 'relax' to (try to) recommend guile-cv ... and
together with guile-studio ... it then really can be said 'try it,
you'll even have fun ...'
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-31 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:13 guile 3 update, halloween edition Andy Wingo
2019-10-30 21:19 ` Christopher Lemmer Webber
2019-10-31 0:01 ` Chris Vine
2019-10-31 16:20 ` Andy Wingo
2019-10-31 17:27 ` Chris Vine
2019-10-31 1:31 ` Nala Ginrut
2019-10-31 1:47 ` Thompson, David
2019-10-31 14:17 ` Mikael Djurfeldt
2019-10-31 16:13 ` Andy Wingo
2019-10-31 14:46 ` David Pirotte [this message]
2019-10-31 16:44 ` Sjoerd van Leent
2019-11-02 5:20 ` Mark H Weaver
2019-11-02 19:33 ` Mark H Weaver
2019-11-03 19:16 ` Andy Wingo
2019-11-03 20:18 ` Mark H Weaver
2019-11-15 9:03 ` Ludovic Courtès
2019-11-15 10:23 ` Andy Wingo
2019-11-16 15:26 ` Ludovic Courtès
2019-11-17 19:33 ` Andy Wingo
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=20191031114653.3854ebcb@capac \
--to=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).