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: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: module system / (oop goops) / :duplicates (merge-generics) / bug?
Date: Sat, 9 Jul 2011 12:08:16 -0300	[thread overview]
Message-ID: <20110709120816.0827236b@rascar> (raw)
In-Reply-To: <87tyav3h7q.fsf@pobox.com>

Hi Andy,

> >>   (default-duplicate-binding-handler
> >>     '(merge-generics replace warn-override-core warn last))
> >
> > This is not 'so important' anymore, but for bug tracking purposes, please note
> > that adding the above in my init.scm file and commenting the #:duplicates (...)
> > expression leads to the known error:

> Git pull, please :).  You still don't have some recent fixes.

I am pulling :) Do you mean I have to checkout an unstable? [if yes, please tell me
what branch/version, I am git [very] 'limited' @ the moment :)

	david@asterix:/usr/local/share/guile/alto/2.0/tests 12 $ guile
	GNU Guile 2.0.2.3-21b6d
	scheme@(guile-user)> (use-modules (mg-3))
	(letstry)
	WARNING: (mg-3): `dialog' imported from both (mg-1) and (mg-2)
	ERROR: In procedure scm-error:
	ERROR: No applicable method for #<<accessor> dialog (1)> in call (dialog #<<widget-a> 8aaa390>)

Thanks,
David

Also, it's not working on this machine either [and I don't uderstand why guile versions
are different? surely I didn't do the right thing with git?]:

	david@rascar:/usr/local/src/guile/git-clone 4 $ git describe
	v2.0.2-7-gae88d9b
	david@rascar:/usr/local/src/guile/git-clone 5 $ git pull
	Already up-to-date.
	david@rascar:/usr/local/src/guile/git-clone 6 $ guile
	GNU Guile 2.0.2.7-ae88d
	...
	scheme@(guile-user)> (default-duplicate-binding-handler)
	$1 = (merge-generics replace warn-override-core warn last)
	scheme@(guile-user)> (use-modules (mg-3))
	(letstry)
	...
	WARNING: (mg-3): `dialog' imported from both (mg-1) and (mg-2)
	ERROR: In procedure scm-error:
	ERROR: No applicable method for #<<accessor> dialog (1)> in call (dialog #<<widget-a> 94c4910>)



  reply	other threads:[~2011-07-09 15:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 21:32 module system / (oop goops) / :duplicates (merge-generics) / bug? David Pirotte
2011-07-06 16:17 ` Ludovic Courtès
2011-07-06 19:22   ` David Pirotte
2011-07-07 11:37     ` Andy Wingo
2011-07-07 16:26       ` David Pirotte
2011-07-07 20:59         ` Andy Wingo
2011-07-08 17:05           ` David Pirotte
2011-07-09 10:02             ` Andy Wingo
2011-07-09 15:08               ` David Pirotte [this message]
2011-07-11 15:49                 ` Andy Wingo
2011-07-12  1:25                   ` David Pirotte
2011-08-18 11:01                     ` Andy Wingo
2011-08-19  5:40                       ` David Pirotte
2011-08-29 17:05                         ` David Pirotte
2011-08-30  2:56                           ` David Pirotte
2011-09-02 11:26                           ` Andy Wingo
2011-09-06 15:41                             ` David Pirotte
2011-08-03 12:28                   ` 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=20110709120816.0827236b@rascar \
    --to=david@altosw.be \
    --cc=bug-guile@gnu.org \
    --cc=ludo@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).