Re: GSoC compiler work, SICL
Sam Steingold <[email protected]> Wed, 21 Mar 2018 20:01:02 -0400
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
Bruno, > * Bruno Haible <[email protected]> [2018-03-21 23:50:04 +0100]: > > - Compiling local functions in a better way requires data-flow analysis; > this would be one outcome of the SICL work. > - Making local functions more debuggable, on the other hand, goes in the > opposite direction, as it prevents some optimizations. That's what the OPTIMIZE declaration is for! http://clhs.lisp.se/Body/d_optimi.htm > In my opinion, > this is much less work than a GSoC project (only ca. 2-4 weeks). Bruno, not everyone is as smart as you are. Alas. I don't know about Charles, but for me it would certainly be more than a month. Moreover, this is not just implementation - one has to update the docs, test the performance impact, learn clisp tool chain &c &c. Thanks. -- Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561 http://steingoldpsychology.com http://www.childpsy.net https://jihadwatch.org http://honestreporting.com http://mideasttruth.com http://www.memritv.org Software is like sex: it's better when it's free. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel