On Thu, May 16, 2013 at 3:42 PM, Juan Jose Garcia-Ripoll <juanjose.garciarip...@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? Cheers, Jason ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
