From: dalanicolai <dalanicolai@gmail.com>
To: guile-user@gnu.org
Subject: Can not create instance of <complex> class
Date: Tue, 11 May 2021 15:14:00 +0200 [thread overview]
Message-ID: <CACJP=3kr1W481LC4Uq8Cd5aWc_x-RMA2GpT1u6BPrcsX+k6pZA@mail.gmail.com> (raw)
Footnote (29) of this page
<https://www.gnu.org/software/guile/manual/html_node/Class-Definition.html>
of the manual mentions that the complex is a predefined class in GOOPS.
However when I try to create an instance of the class using
(use-modules (oop goops))
(define test (make <complex>))
guile raises the following exception:
No applicable method for #<<generic> initialize (9)> in call (initialize
#<instance 7fb5dc535680> ())
Searching in guile's source I do find in in the file goops.scm the line
(define-standard-class <complex> (<number>)).
So my question is why the class is predefined while it is not implemented?
It is only because implementation is not yet finished?
Should I design the class myself?
Thanks for your answers!
reply other threads:[~2021-05-11 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACJP=3kr1W481LC4Uq8Cd5aWc_x-RMA2GpT1u6BPrcsX+k6pZA@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--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).