Re: Amazed by macros working on first attempt
- From: "jonathon" <j_mckitrick@xxxxxxxxxxx>
- Date: 28 Jul 2005 09:51:45 -0700
Zach Beane wrote:
> "Eric Lavigne" <lavigne.eric@xxxxxxxxx> writes:
>
> > 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.
>
> This will also keep you from getting annoyed when things work
> correctly through package internals updates.
Yes, this is the idea. I *could* access any variable from another
package, but if I make these accessors instead, then internal variable
name changes and/or implementation won't affect as much code in other
packages, if any.
This app started out with keyboard input, and I didn't care if a few
menu routines had access to the important objects and variables. In
fact, everything was in one package. Now that I've added another
package to make this a web app, the idea of clearly defined interfaces
makes it more maintainable.
>
> Zach
.
- References:
- Amazed by macros working on first attempt
- From: jonathon
- Re: Amazed by macros working on first attempt
- From: Eric Lavigne
- Re: Amazed by macros working on first attempt
- From: Zach Beane
- Amazed by macros working on first attempt
- Prev by Date: Re: Looking for rudimentary learning exercises
- Next by Date: Re: Writing shared libraries using Lisp
- Previous by thread: Re: Amazed by macros working on first attempt
- Next by thread: Re: Amazed by macros working on first attempt
- Index(es):
Relevant Pages
|
