From: David Pirotte <david@altosw.be>
To: bug-guile@gnu.org
Subject: Fw: module system / (oop goops) / :duplicates (merge-generics) / bug?
Date: Tue, 5 Jul 2011 18:43:41 -0300 [thread overview]
Message-ID: <20110705184341.10088419@rascar> (raw)
Hi again,
[in addition to my just previously posted message]
if after the error following (use-modules (mg-3)) I enter ,q and proceed, here is
what I get [copied from the beginning to show the 'no prompt' as well]:
mg-3.scm:17:2: In procedure letstry:
mg-3.scm:17:2: In procedure module-lookup: Unbound variable: dialog
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
,q
scheme@(guile-user)> (use-modules (mg-1))
scheme@(guile-user)> (use-modules (mg-2))
scheme@(guile-user)> (dialog a)
WARNING: (guile-user): `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> 9979730>)
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]>
;; --
Begin forwarded message:
Date: Tue, 5 Jul 2011 18:32:29 -0300
From: David Pirotte <david@altosw.be>
To: bug-guile@gnu.org
Subject: module system / (oop goops) / :duplicates (merge-generics) / bug?
Hello,
Can someone kindly look at this small example and tell me what's wrong? I get this
david@rascar:~ 8 $ guile
GNU Guile 2.0.0.160-39be
...
scheme@(guile-user)> (use-modules (mg-3))
(letstry)
mg-3.scm:17:2: In procedure letstry:
mg-3.scm:17:2: In procedure module-lookup: Unbound variable: dialog
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
Many thanks,
David
ps: sometimes guile does not 'comeback from an error' with a prompt
invitation, like in my case here above: the guile-prompt only come back
after I enter something, like ,q in this case.
reply other threads:[~2011-07-05 21:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110705184341.10088419@rascar \
--to=david@altosw.be \
--cc=bug-guile@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).