unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: empty default duplicates handler
Date: Wed, 22 Aug 2007 10:24:07 +0200	[thread overview]
Message-ID: <87k5rovuxk.fsf@laas.fr> (raw)
In-Reply-To: <87sl6c4k51.fsf@zip.com.au> (Kevin Ryde's message of "Wed\, 22 Aug 2007 08\:07\:06 +1000")

Hi,

Kevin Ryde <user42@zip.com.au> writes:

> Is it supposed to work to set the default duplicates handling to an
> empty list?

Why not, but we need to define the semantics.

> It seems to work in 1.8, but in the head it's giving
>
> 	=> Unbound variable: map

In `resolve_duplicate_binding ()', we could initialize RESULT to VAR2,
for instance (which would behave like `last', I think).

> I had this in my program as a global setting
>
> 	(default-duplicate-binding-handler '())
>
> Either way if empty isn't allowed it'd be nice to throw an error
> immediately, the same as a bogus handler name symbol does.
>
> The effect I wanted was no work at all done for duplicates checking.
> Modules can override/extend the core by shadowing, but I'm confident
> there's no clashes between my modules and don't want time spent looking
> at that.  Or is '(last) the policy I should be asking for to get that
> non-checking effect?

I think we could do the above change and document that `()' is
equivalent to `(last)'.

What do you think?

Thanks,
Ludovic.



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2007-08-22  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 22:07 empty default duplicates handler Kevin Ryde
2007-08-22  8:24 ` Ludovic Courtès [this message]

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=87k5rovuxk.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.org \
    --cc=user42@zip.com.au \
    /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).