[alexandria-devel] eval-always, defun-always, etc...

[Samium Gromoff]

From: Attila Lendvai <attila.lendvai at 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, still most people prefer COND when
> there are many legs of that if, because in that case COND is much less
> noisy. no new abstraction, only a syntactic sugar, but it's much
> easier for the eye.
> 
> a) has a detailed description why often a full (:compile-toplevel
> :load-toplevel :execute) is necessary, and it'll be even more so as
> XCVB gets used more and more.
> 
> so, i'd suggest to take some action:
> 
>  I) add an eval-always to alexandria-devel
>  II) add a defun-always to alexandria-devel avoid the entire need for a wrapper

No, not the entire need, unless you choose to avoid compile-time use
of all other CL's features.

I.e. if we're to choose a /consistent/ approach, we would be actually
talking about a much wider set of *-always functions.

>  III) ?
> 
> my vote goes for II), which is kinda in sync with c) too.


regards,
  Samium Gromoff
--
                                 _deepfire-at-feelingofgreen.ru
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org