unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Tristan Colgate <tcolgate@gmail.com>
To: guile-user@gnu.org
Subject: duplicate-handlers issue
Date: Tue, 5 Jan 2010 22:05:18 +0000	[thread overview]
Message-ID: <2e6d10881001051405l6415f7fue3d4d7edb131b259@mail.gmail.com> (raw)

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

Hi,

  [This is actually using 1.9, but I think I'm probably doing
something wrong rather than it being a bug]

  I have a module that uses a lazy binder. Under 1.9 it is working
fine but I get warnings about symbol duplication (the lazy binder is
quite aggressive and will match just about anything)under 1.8 I didn't
get the warnings, but they seem reasonable.

  To try and get rid of the warnings I've tried implementing a custom
duplicate-handlers method to defer any duplicates from my lazy binder
to whatever is trying to override them without warnings.

  I am seeing some very odd behaviour. On the initial compile things
work as expected. If I keep deleting ~/.cache it keeps workings. If I
don't delete the cache then it doesnt work and complains about trying
to apply the name of my dupli-removing function. What's even odder is
that if I disable auto-compilation, delete cache, and run it, it
doesn't work either.

  I've reduced it down to the attached files.

  run
  $ guile -L . test.scm
  then run it again

  any help would be very much appreciated.

-- 
Tristan Colgate-McFarlane
----
  "You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"

[-- Attachment #2: testmodule.scm --]
[-- Type: application/vnd.lotus-screencam, Size: 1944 bytes --]

[-- Attachment #3: test.scm --]
[-- Type: application/vnd.lotus-screencam, Size: 68 bytes --]

             reply	other threads:[~2010-01-05 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 22:05 Tristan Colgate [this message]
2010-01-06 14:41 ` duplicate-handlers issue Tristan Colgate

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=2e6d10881001051405l6415f7fue3d4d7edb131b259@mail.gmail.com \
    --to=tcolgate@gmail.com \
    --cc=guile-user@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).