On Mon, Aug 9, 2010 at 3:57 PM, Pascal J. Bourguignon wrote:
> You're right, the problem is with FIND (notice that FIND is a
> function, so that would be in the open-coding of FIND, not a
> macro-expansion):
>
> ---(a.lisp)-
> (defun f (
On Mon, 09 Aug 2010 15:57:18 +0200
p...@informatimago.com (Pascal J. Bourguignon) wrote:
> You're right, the problem is with FIND (notice that FIND is a
> function, so that would be in the open-coding of FIND, not a
> macro-expansion):
This is consistent with what I see as well, the only places w
Juan Jose Garcia-Ripoll writes:
> On Sun, Aug 1, 2010 at 4:24 PM, Pascal J. Bourguignon
> wrote:
>> I guess if the optimizer determines that a variable is of a given
>> type, it should also initialize with a value valid for that type.
>
> No, this is the resposability of the programmer. (LET (A
On Sun, Aug 1, 2010 at 4:24 PM, Pascal J. Bourguignon
wrote:
> I guess if the optimizer determines that a variable is of a given
> type, it should also initialize with a value valid for that type.
No, this is the resposability of the programmer. (LET (A)) is
equivalent to (LET ((A NIL))) not jus
I guess if the optimizer determines that a variable is of a given
type, it should also initialize with a value valid for that type.
---(a.lisp)-
(eval-when (:compile-toplevel)
(print (list (lisp-implementation-type)
(
