From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: guile-user@gnu.org
Subject: Re: GOOPS %modify-[instance|class]
Date: Fri, 10 Jan 2003 11:12:02 +0100 [thread overview]
Message-ID: <xy7ptr5nwjx.fsf@nada.kth.se> (raw)
In-Reply-To: <200301082151.59431.clinton@unknownlamer.org> (Clinton Ebadi's message of "Wed, 8 Jan 2003 21:51:59 -0500")
Clinton Ebadi <clinton@unknownlamer.org> writes:
> I think %modify-instance and -class should be public.
Could you be more specific why? These seem pretty strange and magical
to me, and might change as the implementation evolves...
> I specialized change-class and change-object-class (to the same
> thing, just to be safe because the manual says either one may be
> called but not both).
The manual shouldn't mention change-object-class since that is a
private part of the implementation. BTW, change-class is a generic
function while change-object-class is a prociedure.
> I seem to have a problem: when I return the updated class, all my
> pointers to the old class are invalidated! And then it seems that
> GOOPS continues in an infinite loops updated the same objects over
> and over again.
Could you please explain what you want to do. You talk about
returning an updated class. But this only happens if one is using
change-class to change the metaclass of a class instance. The normal
job for change-class is to change the class of an instance.
Here's an example of specialization to change-class:
(define-class <class-change-notice-class> (<class>))
(define-method (change-class (o <object>) (c <class-change-notice-class>))
(next-method)
(format #t "class changed for instance ~A\n" o))
(define-class c () (x) #:metaclass <class-change-notice-class>)
(define o (make c))
;;; Now we redefine c:
(define-class c () (x) (y) #:metaclass <class-change-notice-class>)
;;; If we now refer to o, it will be lazily updated:
o
-->
class changed for instance #<c 807f890>
#<c 807f890>
This seems to work.
Could you please give me enough information to reproduce the infinite
loop you are talking about?
Best regards,
Mikael Djurfeldt
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-01-10 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 2:51 GOOPS %modify-[instance|class] Clinton Ebadi
2003-01-10 10:12 ` Mikael Djurfeldt [this message]
2003-01-12 21:45 ` Clinton Ebadi
2003-01-15 12:38 ` Mikael Djurfeldt
-- strict thread matches above, loose matches on Subject: below --
2003-01-20 4:01 Clinton Ebadi
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=xy7ptr5nwjx.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--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).