Re: Is the following behavior defined by the standard or implementation specific?
- From: Robert Uhl <eadmund42@xxxxxxxxxxxxxxx>
- Date: Mon, 30 Jul 2007 09:55:27 -0600
"Thomas F. Bur***" <tbur***@xxxxxxxxx> writes:
One last note: you might be interested in the sb-ext:*derive-function-
types* switch in SBCL. It gives a slightly different and non-ANSI
behavior to type declarations: it more or less declaims the ftype that
the compiler is able to inference whenever you define a function. So
you can write code like:
(defun sss (x y)
(declare (double-float x y))
(+ x y))
And it would have the same effect as the ftype declaration you gave
above.
Ooooh--nice. I'll have to play with that some. I wonder if it'd also
do the warning-if-redefined-incompatibly bit. That could actually be
pretty sweet.
--
Robert Uhl <http://public.xdi.org/=ruhl>
Even you automobilists can spot where this is going, right? Mountain
bikes are the SUVs among bicycles. --Maarten Wiltink
.
- Follow-Ups:
- Re: Is the following behavior defined by the standard or implementation specific?
- From: John Thingstad
- Re: Is the following behavior defined by the standard or implementation specific?
- References:
- Is the following behavior defined by the standard or implementation specific?
- From: Jason Nielsen
- Re: Is the following behavior defined by the standard or implementation specific?
- From: Thomas F. Bur***
- Is the following behavior defined by the standard or implementation specific?
- Prev by Date: Re: Is Lisp a Blub?
- Next by Date: Re: Is the following behavior defined by the standard or implementation specific?
- Previous by thread: Re: Is the following behavior defined by the standard or implementation specific?
- Next by thread: Re: Is the following behavior defined by the standard or implementation specific?
- Index(es):