For various reasons, the most pain-free way for me to use lisp in my
current work environment is to deliver scripts as runnable executables.
There is no development budget to speak of, so the easiest way for me
to control the size of an .exe is to limit my library dependencies (as
opposed to getting a fancy-schmancy lisp can strip the unneeded stuff out).
However, I also am trying to make my packages "big tents" for related
code. What I am thinking of doing is using the package loaded in some base
system to export the entire set of symbols I want to expose, but use many
other system definitions to partition the package based (partially) on the
dependencies it requires.
One problem I can see right away is that it might be hard to see what
systems need loaded for a certain subset of the functionality to be
available.
Comments and suggestions welcome.
Matt
--
"You do not really understand something unless you
can explain it to your grandmother." -- Albert Einstein.
On Nov 15, 10:55 am, "Matthew D. Swank" <··················@gmail.com>
wrote:
> the easiest way for me
> to control the size of an .exe
Does anyone still care? I mean, obviously if the binary was 300M or
something, but not if it's 10 or 20.