unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: 20093@debbugs.gnu.org
Subject: bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error
Date: Sun, 3 Jul 2016 19:10:07 -0300	[thread overview]
Message-ID: <20160703191007.0e4d2471@capac> (raw)
In-Reply-To: <87k2hfopyc.fsf@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]

Hello Andy,

Further to the previous answer [of July the 2th 2016]

> ...
> But, you say, I only specified the duplicates handler after loading
> goops!  Well indeed, but if a module didn't specify #:duplicates, its
> duplicates handling was implicitly dynamically scoped to whatever the
> current default-duplicates-handlers were.  That seems bogus to me: the
> module declares its imports and exports and a lack of a declaration of
> #:duplicates indicates that the module is implicitly specifying the
> duplicate handlers that are described in the manual.

I disagree with the way you [now' re-] interpret things: if a module has no
#:duplicates declaration, it is implicitly specifying the duplicate handlers 
returned by (default-duplicate-binding-handler), _not_ the one from the
manual.

IMO, this was an API, and for me, a hard coded list instead of querying an API does
not offer any advantage, at the contrary, a step backward in 'power'.

> In master I have changed the `default-duplicate-binding-handler' to
> simply access the handlers for the current module, as that seems to be
> the correct thing.  Let me know how it goes!  Closing as done but let's
> follow up :)

This breaks all my code, with no other option but maintaining my own
boot-9 version: I really wish I can avoid that, could you reconsider? [no, I don't
want to have to use #:duplicates, since I _always_ [like always always always] want
my modules to grab my global setting and default].

As you understood by now, I need 2 things wrt duplicate handlers:

	1.	I must be able to patch guild, so it ,use (oop goops) and set
		these before I compile my modules [with or without --no-auto-compile
		does not matter]. All my scripts do so as well of course [1]

		#!/bin/sh
		# -*- scheme -*-
		exec ${GUILE:-/opt2/bin/guile} --no-auto-compile -e '(@@ (guild) main)' -s "$0" "$@"
		!#

		(eval-when (expand load eval)
		  (use-modules (oop goops))
		  (default-duplicate-binding-handler
		    '(merge-generics replace warn-override-core warn last)))

		...

		This does not work anymore, I hope it can be fixed

	2.	obviously, the above only make sense if modules grab
		(default-duplicate-binding-handler) when no #:duplicates declaration

		I can maintain my own boot-9 but wish to avoid this solution.

Cheers,
David

[1] http://git.savannah.gnu.org/cgit/grip.git/tree/grip/clutter/examples/bouncer.in

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-07-03 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  3:17 bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error David Pirotte
2016-06-23 16:00 ` Andy Wingo
2016-07-03  4:57   ` David Pirotte
2016-07-03 22:10   ` David Pirotte [this message]
2016-07-07  9:54     ` Andy Wingo
2016-07-03 20:55 ` bug#20093: Fw: " David Pirotte
2016-07-07 10:22   ` Andy Wingo
2016-07-25  2:38     ` David Pirotte
2016-07-25  2:44       ` David Pirotte

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=20160703191007.0e4d2471@capac \
    --to=david@altosw.be \
    --cc=20093@debbugs.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).