🚀 go-pugleaf

Hi Doug!

I personally prefer the DEFSYSTEM approach. i've been using it for 7+
years. if you are just a little careful about your code organization,
it's fairly easy to deal with. I have a simple guideline for what goes
where in the defsystem:

first module contains macros ONLY. this module must be compiled AND
loaded before continuing.

second module contains things like Classes ONLY. like compiled and
loaded. 

third module contains DEFVARs and SETQs of the defvars. if you just
use (DEFVAR *global-var*) or (DEFVAR *global-var* NIL "doc-string")
then a file of these things can precede module 1 or 2 if you want
macros or classes to use global symbols. otherwise, as module 3, the
defvars can be assigned make-instances of the classes.

fourth and subsequent modules can now use macros, classes, and
globals. I NEVER put macros, classes or DEFVARs anywhere except the
first three modules (generally, these are single files of the three
things). meta-. will find things for me with no trouble, so the could
get organized differently, but i've found this technique to be safest
for me over the years.

it keeps me out of trouble in case I forget the compile/load ordering
of the other modules.

 -- clint
--

Clint Hyde		"Give me a LispM or give me death!" -- anonymous

Advanced Decision Systems	Internet:  chyde@chesapeake.ads.com
2111 Wilson Blvd #800
Arlington, VA 22201		(703) 875-0327