[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
namespaces, goops, etc.
From: |
Lars J. Aas |
Subject: |
namespaces, goops, etc. |
Date: |
Fri, 3 Nov 2000 17:18:53 +0100 |
User-agent: |
Mutt/1.2.5i |
Hi guys,
A couple of things I'm wondering about:
I've noticed I can use the module system's "define-public" inside functions
and get internal definitions exported to the toplevel namespace.
(define (some-function)
(define (some-internal-function)
(define-public (some-internal-internal-function)
(display "some-internal-internal-function\n")))
(some-internal-function))
(some-function)
(some-internal-internal-function)
I'm curious on whether this is just a side-effect of the implementation of
the module system, or if it is supposed to work like this and people can take
advantage of it?
Another thing I've noticed is that generic goops methods has to be defined
in the toplevel namespace. Was there a reason for this design decision, other
than perhaps making the goops module easier to implement (global variables and
stuff?)? Just wondering - it's not a feature I miss or anything, although I
can imagine it could be useful with local generic methods in certain
circumstances...
Lars J
- namespaces, goops, etc.,
Lars J. Aas <=
- Re: namespaces, goops, etc., thi, 2000/11/03
- Re: namespaces, goops, etc., Michael Livshin, 2000/11/03
- Re: namespaces, goops, etc., Lars J. Aas, 2000/11/03
- Re: namespaces, goops, etc., Michael Livshin, 2000/11/03
- Re: namespaces, goops, etc., Lars J. Aas, 2000/11/03
- Re: namespaces, goops, etc., Michael Livshin, 2000/11/03
- Re: namespaces, goops, etc., Lars J. Aas, 2000/11/03
- Re: namespaces, goops, etc., Lars J. Aas, 2000/11/03
- Re: namespaces, goops, etc., Mikael Djurfeldt, 2000/11/06
- Re: namespaces, goops, etc., Michael Livshin, 2000/11/07