(I do agree foo-syntax.lisp and foo.lisp (or early-foo.lisp and
foo.lisp -- whatever) style has much to recommend itself.)
ok, i seem to read out an agreement from the last few mails... so,
how about this:
- where required, split files to foo.lisp, foo-early.lisp and use
:compile-depends
dear list,
i know that this is a subject that has strong feelings attached to,
but with recent developments in XCVB the need for (eval-when
(:compile-toplevel :load-toplevel :execute) ...) has rose, and seeing
numerous eval-when noise in the code is potentially annoying.
related material:
a)
On Oct 16, 2009, at 09:50 , Attila Lendvai wrote:
I) add an eval-always to alexandria-devel
II) add a defun-always to alexandria-devel avoid the entire need for
a wrapper
III) ?
Don't add any of these kludges, and instead reorganize code such that
EVAL-WHEN is not sprinkled throughout
Michael Weber michaelw+alexand...@foldr.org writes:
On Oct 16, 2009, at 09:50 , Attila Lendvai wrote:
I) add an eval-always to alexandria-devel
II) add a defun-always to alexandria-devel avoid the entire need for
a wrapper
III) ?
Don't add any of these kludges, and instead
From: Attila Lendvai attila.lend...@gmail.com
[snip]
c) makes it clear that Nikodemus doesn't like eval-always, and i'm
sure many other lispers are on the same opinion. for the argument that
it does not introduce a new abstraction, i can point to COND, which is
the same as an ugly IF ladder,
Don't add any of these kludges, and instead reorganize code such that
EVAL-WHEN is not sprinkled throughout the code.
IOW, you propose that the current way of categorizing definitions into
separate files should be changed so that it is based on evaluation
stages.
this is certainly a cleaner
: Michael Weber michaelw+alexand...@foldr.org
Don't add any of these kludges, and instead reorganize code such that
EVAL-WHEN is not sprinkled throughout the code.
: Attila Lendvai attila.lend...@gmail.com
IOW, you propose that the current way of categorizing definitions into
separate files
On Oct 16, 2009, at 12:30 , Faré wrote:
: Michael Weber michaelw+alexand...@foldr.org
Don't add any of these kludges, and instead reorganize code such
that
EVAL-WHEN is not sprinkled throughout the code.
: Attila Lendvai attila.lend...@gmail.com
IOW, you propose that the current way of
