From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: srfi-9 record type checking
Date: Tue, 13 Jun 2006 00:00:50 +0100 [thread overview]
Message-ID: <87fyiat1wd.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87lks8rudq.fsf@laas.fr> ( Ludovic Courtès's message of "Thu, 08 Jun 2006 09:14:57 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> I vote for just fixing record-accessor to be strict by default;
>> i.e. treating current behaviour as a bug. I'd be surprised if anyone
>> was relying on this, and if they are it's easy to code a workaround.
>
> The issue is that this would impact people that use records directly
> (i.e., not via SRFI-9) and although this `#f' behavior is undocumented,
> they may well have come to rely on it.
Yes, that is indeed the issue. I just think that (i) your "may" is
extremely unlikely, and/because (ii) the current behaviour is
sufficiently odd that we can see it as a bug - for which there is
obviously no back-compatibility requirement - instead of as
"behaviour", and (iii) the nature of 'record-accessor' is such that it
can be fixed up in just one place if someone really does want the old
behaviour:
(define new-record-accessor record-accessor)
(set! record-accessor
(lambda (type field)
(lambda (obj)
(and ((record-predicate type) obj)
((new-record-accessor type field) obj)))))
So on balance I don't think we need to provide complete compatibility
within Guile here.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-06-12 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 23:19 srfi-9 record type checking Kevin Ryde
2006-06-07 16:42 ` Ludovic Courtès
2006-06-07 22:18 ` Neil Jerram
2006-06-07 23:21 ` Kevin Ryde
2006-06-08 7:14 ` Ludovic Courtès
2006-06-12 23:00 ` Neil Jerram [this message]
2006-06-13 7:26 ` Ludovic Courtès
2006-08-02 0:42 ` Kevin Ryde
2006-08-22 9:37 ` Ludovic Courtès
2006-08-25 1:04 ` Kevin Ryde
2006-06-07 23:31 ` Kevin Ryde
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=87fyiat1wd.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).