From: Stefan Israelsson Tampe <INVALID.NOREPLY@gnu.org>
To: Neil Jerram <neil@ossau.uklinux.net>,
Andy Wingo <wingo@pobox.com>,
Michael Burschik <Michael.Burschik@gmx.de>,
Stefan Israelsson Tampe <stefan.itampe@gmail.com>,
bug-guile@gnu.org
Subject: [bug #25525] Segfault using goops
Date: Sun, 21 Aug 2011 10:54:42 +0000 [thread overview]
Message-ID: <20110821-105442.sv78157.94899@savannah.gnu.org> (raw)
In-Reply-To: <20110820-181456.sv78157.79619@savannah.gnu.org>
Follow-up Comment #6, bug #25525 (project guile):
I recognized that the layout problem appears as well if you inherit
from first <class> and then a class <b> which does not contain <class> I did
fix this. By postponing the addition of <class> variables to the last in order
for them to always get the correct
index in the layout.
So, now
(1) you can inheret meta objects from both <class> and non <class> objects
(2) it's not possible to inherit or add variables that have the same name as
<class> variables. If that is tried an error is signaled.
For a git-diff, see goopsdiff2 below
(file #23843)
_______________________________________________________
Additional Item Attachment:
File name: goopsdiff2.diff Size:4 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25525>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2011-08-21 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 8:25 [bug #25525] Segfault using goops Michael Burschik
2009-02-09 23:17 ` Neil Jerram
2010-04-16 11:26 ` Stefan Israelsson Tampe
2010-04-16 11:36 ` Stefan Israelsson Tampe
2010-06-07 10:00 ` Andy Wingo
2011-08-20 18:14 ` Stefan Israelsson Tampe
2011-08-21 10:54 ` Stefan Israelsson Tampe [this message]
2011-09-05 12:25 ` Stefan Israelsson Tampe
2011-10-20 22:32 ` bug#9815: " Andy Wingo
2011-09-02 17:57 ` Andy Wingo
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=20110821-105442.sv78157.94899@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=Michael.Burschik@gmx.de \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=stefan.itampe@gmail.com \
--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).