[Ecls-list] Function type proclaimations not working?

Jason Sewall jasonsewall at gmail.com
Thu May 16 22:51:39 UTC 2013

On Thu, May 16, 2013 at 3:42 PM, Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at gmail.com> wrote:
> You are looking at the _old_ manual. That section is obsolete, but I did not
> have time to go through the whole manual again.

Sorry, it wasn't clear to me that it was "old" - I got it from a doc
tree I recently built from the ecl-doc repo. Should such parts be at
least marked with *obsolete* somehow if there is no time for updating?

> That said, ECL no longer implements unboxed functions. It was very hard to
> maintained and lead to code bloat: we had to provide two functions for every
> signature, one with Common Lisp objects, another one with unboxed values. It
> could be reimplemented using appropriate proclamations, but the default
> action was to remove it.
> Outside from function arguments, the rest can be fully unboxed, as you see
> in the new code body, which is also more readable.

This seems sensible to me, but it doesn't really explain the warning I
got, does it? Shouldn't the compiler just ignore the proclamation in
that case instead of apparently failing to understand it?


More information about the ecl-devel mailing list