CLISP GSoC project ideas

Hi Sam,

Before we offer a GSoC project to a specific volunteer, I think we should
collect ideas and see how promising they are.

What are criteria for promising ideas?
  - Don't require too much learning about clisp internals.
  - Be feasible.
  - Require 2-4 months of work.

Ideas I can think of / am aware of:

[from https://clisp.sourceforge.io/wanted.html]
* Remaining work on multithreading: too much learning, too big (2 man-years)
* Multithreaded hash tables: IMO pointless, locking is the way to go
* Octave binding: learning and sizing probably ok, but is it appealing?
* IEEE NaNs and infinities: too small (2 man-weeks)
* Embed clisp: too big (1 man-year)
* Native file compilation: too big (2 man-years)
* Native just-in-time compilation via llvm, libgccjit, or eclipse omr: too big
  (1-2 man-years)
* Compilation to JVM: already done by Clojure, pointless for clisp
* GUI: too big
* SSL bindings: too small (2-4 man-weeks)

[other]
* Source-level debugging with breakpoints in SLIME
  (or is this already done? I don't know)
* Enhance the compiler to do inlining of local functions
  - IMO infeasible without rewriting the compiler frontend to include data
    flow analysis.
* Integrate Robert Strandh's SICL compiler frontend with clisp's bytecode
  backend

Do you have other ideas? Other learning or sizing estimations?

Bruno


------------------------------------------------------------------------------
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