From: "Diogo F. S. Ramos" <dfsr@riseup.net>
To: David Pirotte <david@altosw.be>
Cc: guile-user@gnu.org
Subject: Re: #:getter procedure returns unexpected value in GOOPS
Date: Sat, 26 Apr 2014 19:58:48 -0300 [thread overview]
Message-ID: <87fvkzhf4n.fsf@nebulosa.milkyway> (raw)
In-Reply-To: <20140426191909.3902016f@capac> (David Pirotte's message of "Sat, 26 Apr 2014 19:19:09 -0300")
>> I tried changing all to `#:init-value', but the result was the same.
>
> Imo, using your definitions, guile should return 'foo, not 42.
IMO it should return 'bar, as `foo-a' should return the value of the
slot `a', which in the subclass <bar> of <foo> is 'bar.
next prev parent reply other threads:[~2014-04-26 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 23:24 #:getter procedure returns unexpected value in GOOPS Diogo F. S. Ramos
2014-04-26 12:26 ` Neil Jerram
2014-04-26 17:35 ` Diogo F. S. Ramos
2014-04-26 22:19 ` David Pirotte
2014-04-26 22:58 ` Diogo F. S. Ramos [this message]
2014-04-27 22:14 ` David Pirotte
2014-04-27 1:15 ` Mark H Weaver
2014-04-27 22:14 ` David Pirotte
2014-04-28 1:12 ` Mark H Weaver
2014-05-02 4:36 ` David Pirotte
2015-03-09 21:58 ` Andy Wingo
2015-04-23 22:56 ` 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=87fvkzhf4n.fsf@nebulosa.milkyway \
--to=dfsr@riseup.net \
--cc=david@altosw.be \
--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).