Re: Amazed by macros working on first attempt
- From: "Eric Lavigne" <lavigne.eric@xxxxxxxxx>
- Date: 28 Jul 2005 08:09:32 -0700
>I wanted one package to have access to values from another, but I
>didn't want to export/expose the variables. So, I decided to add
>accessor functions and create a new 'interface.lisp' module.
I don't understand what your macros are doing, but accessing variables
that aren't exported sounds rather easy.
Accessing exported variable:
mypackage:*exported-variable*
Accessing variable that is not exported:
mypackage::*internal-variable-that-you-shouldnt-touch*
If you are annoyed by the idea of encapsulation, in which a package
maintainer decides which variables you should or shouldn't touch, then
just use the double colon all the time. mypackage::*exported-variable*
works just fine.
.
- Follow-Ups:
- Re: Amazed by macros working on first attempt
- From: Zach Beane
- Re: Amazed by macros working on first attempt
- References:
- Amazed by macros working on first attempt
- From: jonathon
- Amazed by macros working on first attempt
- Prev by Date: Re: UFFI and calling Lisp functions from foreign code
- Next by Date: Re: How do you imagine future Common Lisp standard ?
- Previous by thread: Amazed by macros working on first attempt
- Next by thread: Re: Amazed by macros working on first attempt
- Index(es):