Commit 6a0b694e authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

more TODO items

parent 5aadede4
......@@ -41,10 +41,10 @@ TODO for cl-launch as of 4.0.1.6
dispatched-entry would populate a data structure bound to
cl-launch::*dispatched-entry* and call a restart function
cl-launch::dispatched-restart that uses (argv0) on supported
platforms -- error out on unsupported platforms.
platforms or via cl-launch launcher -- error out on unsupported platforms.
http://www.xach.com/lisp/buildapp/
* Support these other options from Xach's buildapp:
* Support these other options from Xach's buildapp?
--load-path --asdf-path --asdf-tree --manifest-file --logfile
* Maybe add these SBCL-specific options, too?
......@@ -61,3 +61,17 @@ TODO for cl-launch as of 4.0.1.6
* --core-only
That's hard to add, not that useful, and may require hacking
both uiop and cl-launch to get it right. Lots of pain, no gain.
* Better dependencies for --file and --eval
** Create an implicit in-memory system cl-launch/file-1, etc.,
with a single file component, for each --file argument.
** Have it depend on all the previous systems and files, so dependencies work.
** Don't bother counting --eval, though, since there's no file to timestamp;
Document for the user that they are on their own if a change in
such --eval change the meaning of subsequent fasl files;
they may have to manually clear their cache.
** Provide a --force option to force recompilation?
** on ECL, we still have to create temporary files for --eval,
but we still don't want to have other systems depend on them
except the top-level one.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment