From: Andy Wingo <wingo@pobox.com>
To: Hans Aberg <haberg-1@telia.com>
Cc: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: GIT version: values writing
Date: Wed, 26 Jan 2011 21:57:12 +0100 [thread overview]
Message-ID: <m3ipxbcriv.fsf@unquote.localdomain> (raw)
In-Reply-To: <140431E4-7361-4F1B-A0E4-199E1272E67A@telia.com> (Hans Aberg's message of "Thu, 20 Jan 2011 17:51:51 +0100")
On Thu 20 Jan 2011 17:51, Hans Aberg <haberg-1@telia.com> writes:
> However, quietly loosing values is inviting bugs.
True. Common Lisp does it though, FWIW. I find it convenient.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-01-26 20:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 9:57 GIT version: values writing Hans Aberg
2011-01-19 14:44 ` GIT version: values Hans Åberg
2011-01-26 20:51 ` Andy Wingo
2011-01-26 23:34 ` Hans Aberg
2011-01-27 9:00 ` Andy Wingo
2011-01-27 13:20 ` Hans Aberg
2011-01-19 17:05 ` Hans Aberg
2011-01-20 15:17 ` Ludovic Courtès
2011-01-20 17:10 ` Hans Aberg
2011-01-19 19:40 ` GIT version: segmentation fault Hans Aberg
2011-01-26 20:46 ` Andy Wingo
2011-01-26 23:37 ` Hans Aberg
2011-01-19 22:22 ` GIT version: missing linking flag Hans Aberg
2011-01-20 15:20 ` Ludovic Courtès
2011-01-20 17:03 ` Hans Aberg
2011-01-20 21:01 ` Ludovic Courtès
2011-01-20 21:13 ` Hans Aberg
2011-01-21 16:02 ` Ludovic Courtès
2011-01-21 17:59 ` Hans Aberg
2011-01-26 20:52 ` Andy Wingo
2011-01-26 23:44 ` Hans Aberg
2011-01-29 21:47 ` Ludovic Courtès
2011-01-29 22:51 ` Hans Aberg
2011-01-26 20:55 ` Andy Wingo
2011-01-26 23:47 ` Hans Aberg
2011-01-20 15:16 ` GIT version: values writing Ludovic Courtès
2011-01-20 16:51 ` Hans Aberg
2011-01-20 21:18 ` Ludovic Courtès
2011-01-20 21:55 ` Hans Aberg
2011-01-21 17:13 ` Values extension Hans Aberg
2011-01-26 20:57 ` Andy Wingo [this message]
2011-01-26 23:50 ` GIT version: values writing Hans Aberg
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=m3ipxbcriv.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=haberg-1@telia.com \
--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).