[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Possible bug with re-export, :select and GOOPS accessors?!
From: |
Thomas Wawrzinek |
Subject: |
Possible bug with re-export, :select and GOOPS accessors?! |
Date: |
Wed, 22 Aug 2001 11:57:04 +0200 (MEST) |
Hi!
Using two classes in two modules, one inheriting from the other an accessor,
I got problems when trying to use the accessor *and* using :select on the
:use-module option.
A short example is appended.
I've seen this behavior with the recently announced 1.5.1. Not tested with
any other version.
How is re-export intended to behave?
Regards,
Thomas
;; Example code
(define-module (m1)
:use-module (oop goops))
(define-class <foo> ()
(x #:init-value 0 #:accessor x-value))
(export <foo> x-value)
(define-module (m2)
:use-module (oop goops)
:use-module (m1))
(define-class <bar> (<foo>)
)
(re-export x-value)
(export <bar>)
;; This works.
;(define-module (main)
; :use-module (oop goops)
; :use-module (m2))
;; This yields 'ERROR: no binding `x-value' in module (m2)' ...
(define-module (main)
:use-module (oop goops)
:use-module ((m2) :select (<bar> x-value)))
(define o (make <bar>))
(display (x-value o)) (newline)
- Possible bug with re-export, :select and GOOPS accessors?!,
Thomas Wawrzinek <=