* MOP bug?
@ 2002-04-29 17:03 Michael Burschik
0 siblings, 0 replies; 2+ messages in thread
From: Michael Burschik @ 2002-04-29 17:03 UTC (permalink / raw)
If I call guile interactively and type this:
(use-modules (oop goops))
(define-class <thing> () (slot1))
(define-method (slot-unbound (c <class>) (o <thing>) s)
(display "You can't do that.\n"))
(define mything (make <thing>))
(slot-ref mything 'slot1)
I get what I want. If I put the above statements in a file and execute guile
-f file or guile -s file, I get this error message:
ERROR: In procedure class-direct-methods:
ERROR: Wrong type argument in position 1: #<struct 40209640:40209640>
Now why should that be?
I am using guile 1.4, goops 1.0.2 and linux 2.4.
Regards
Michael Burschik
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MOP bug?
@ 2002-04-30 15:49 Thomas Wawrzinek
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Wawrzinek @ 2002-04-30 15:49 UTC (permalink / raw)
Cc: bug-guile
Hi!
michael.burschik@gmx.de writes:
> I get what I want. If I put the above statements in a file and execute guile
> -f file or guile -s file, I get this error message:
>
> ERROR: In procedure class-direct-methods:
> ERROR: Wrong type argument in position 1: #<struct 40209640:40209640>
Try adding
(define-module (guile-user))
to the top of your script.
[This should be fixed in 1.5.x and CVS.]
HTH,
Thomas
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-04-30 15:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-29 17:03 MOP bug? Michael Burschik
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 15:49 Thomas Wawrzinek
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).