From: Clinton Ebadi <clinton@unknownlamer.org>
Subject: GOOPS %modify-[instance|class]
Date: Wed, 8 Jan 2003 21:51:59 -0500 [thread overview]
Message-ID: <200301082151.59431.clinton@unknownlamer.org> (raw)
I think %modify-instance and -class should be public.
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). 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.
goops.c is using SCM_CAR and SCM_CDR to write to the cell of memory itself.
Maybe I could use the low level object struct and modify it somehow?
--
http://unknownlamer.org
The root of unspoken fear
The root grows deep in my heart
A dark cold sound tears at my life
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2003-01-09 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 2:51 Clinton Ebadi [this message]
2003-01-10 10:12 ` GOOPS %modify-[instance|class] Mikael Djurfeldt
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=200301082151.59431.clinton@unknownlamer.org \
--to=clinton@unknownlamer.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).