unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: goops - guile-clutter unexpected bug while using #:virtual slot allocation for a <clutter-actor> subclass
Date: Tue, 27 Jan 2015 17:11:15 -0200	[thread overview]
Message-ID: <20150127171115.6172ccea@capac> (raw)
In-Reply-To: <87sieweie4.fsf@pobox.com>

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

Hello Andy,

	- we should not have mixed the 'accessor' problem as reported by
	another user and the setter bug I reported [on irc];

	- also I should have reported a separate bug to bug-guile@gnu.org, but I
	thought we perfectly understood each other, I was wrong and we got confused,
	my bad.

> >>  Can you make a test case without guile-gnome?
> >
> > No, it is a guile-gnome problem/bug, so here below, a very short test case (*)
> 
> OK, then please file it in the guile-gnome bugzilla.  Thanks.  We
> probably don't need to talk about it on guile-devel.

Ok, will do.

> The setters inheritance bug is fixed to be like 1.8.

Thanks, it _does_ work as expected now, now as in using the latest stable-2.0! my
apologies [wrt our irc chat today] because I was dead sure I did check [2 days ago]
with the latest stable-2.0, and it appears I was still using the detached... It
happens, but I am sorry.

>  I'll write another mail, but briefly the idea is this: an accessor on a slot (or
> a getter, or a setter), declared via #:accessor or #:getter or #:setter, is used
> to access the value of the slot in which it is declared.  However not
> all subclasses of a class have all slots of their superclasses;
> consider:
> ...

Yes, of course, but this answer totally confused me: what you are talking about
here and the code you are using has nothing to do with the setter bug I reported on
irc and for which I pasted a specific short test case, I got really confused here.

Happy hacking,
David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-01-27 19:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 19:46 goops - guile-clutter unexpected bug while using #:virtual slot allocation for a <clutter-actor> subclass David Pirotte
2014-12-19 23:42 ` Panicz Maciej Godek
2014-12-20  6:16   ` David Pirotte
2015-01-26 21:35 ` Andy Wingo
2015-01-27  1:00   ` David Pirotte
2015-01-27  8:29     ` Andy Wingo
2015-01-27 19:11       ` David Pirotte [this message]
2015-01-27 19:35         ` David Pirotte
2015-01-27 20:44         ` Andy Wingo
2015-01-28  3:05           ` David Pirotte
2015-01-28  3:36             ` David Pirotte
2015-01-28 12:57             ` Andy Wingo
2015-01-28 19:24               ` David Pirotte
2015-01-30 13:50           ` David Pirotte
2015-02-06 13:33             ` Andy Wingo
2015-02-06 17:09               ` David Pirotte
2015-02-06 17:49                 ` Andy Wingo
2015-02-07  0:06                   ` David Pirotte
2015-02-07 15:37                     ` Andy Wingo
2015-02-07 17:13                       ` David Pirotte
2015-02-07 16:08                     ` David Pirotte
2015-02-04 16:12           ` 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=20150127171115.6172ccea@capac \
    --to=david@altosw.be \
    --cc=guile-devel@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).