From: Brent Pinkney <brp@4dst.com>
To: guile-devel@gnu.org
Subject: Help required with exporting and using GOOP generics
Date: Thu, 14 Mar 2013 12:55:11 +0200 [thread overview]
Message-ID: <5141AC8F.8030407@4dst.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
Hello,
I am having serious problems exporting generics from subclasses of
<object> and then using them in other modules.
I have trawled the logs and tried every combination I can thing of.
I have tried creating a common base class <thing> for all my classes and
defining the methods there, I have tried exporting generics, and I have
even tried every combination of #:duplicates (merge-generics, first,
last. etc.).
I can sometimes make some progress but eventually I grind to a halt -
often with spurious error messages saying that "format" and "for-each"
are not memoized.
I am also quite willing to rework my code to fit guile - I just need
some help on how to proceed.
Basically I would like a class hierarchy.
Module Class
-------------------------------------
<object>
(brent thing) <thing> ; optional - let me know
id name name!
(brent foo) <foo>
; redefines from <thing>
id name name!
"same file" <bar>
; uses thing.name!
(brent baz) <baz>
; redefines from <thing>
name name!
I would then like a common module (brent main) to import (brent thing)
(brent foo) and (brent baz) and then merrily create and use these classes.
Please can someone provide me with the recipe that will solve the above
and also scale to a proper large system.
(I have test code - if required)
Thanks
Brent
[-- Attachment #2: Type: text/html, Size: 2447 bytes --]
next reply other threads:[~2013-03-14 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 10:55 Brent Pinkney [this message]
2013-03-14 18:27 ` Help required with exporting and using GOOP generics David Pirotte
2013-03-14 21:42 ` Mark H Weaver
2013-03-15 0:11 ` dsmich
2013-03-15 20:57 ` Brent Pinkney
2013-03-15 21:05 ` Mark H Weaver
2013-03-15 21:45 ` Mark H Weaver
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=5141AC8F.8030407@4dst.com \
--to=brp@4dst.com \
--cc=guile-devel@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).