From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: bug-guile@gnu.org, guile-devel@gnu.org
Subject: Re: GOOPS bug found?
Date: 07 May 2002 20:19:52 +0200 [thread overview]
Message-ID: <ab9ek0$nml$2@main.gmane.org> (raw)
In-Reply-To: <87sn5uce57.fsf@alice.rhinosaur.lan>
Andreas Rottmann <a.rottmann@gmx.at> writes:
> As my C++ <-> Guile bindings (ucxx.sf.net) are approaching
> completeness, I have run into another strange problem. I have managed
> to isolate the code that causes it and wrote a self-contained C
> program that exposes the bug.
Thanks! I have recorded this as bug 'goops-1'. I haven't looked at
it yet. If you can investigate this further, that would be great...
please refer to bug 'goops-1' if you have some followup.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-07 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 19:35 GOOPS bug found? Andreas Rottmann
2002-04-17 20:01 ` Andreas Rottmann
2002-05-07 18:19 ` Marius Vollmer [this message]
[not found] ` <87offrlt13.fsf@zagadka.ping.de>
2002-05-12 13:17 ` Andreas Rottmann
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='ab9ek0$nml$2@main.gmane.org' \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@gnu.org \
--cc=guile-devel@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).