Commit 72c928ca authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files
parents ea413e78 0f57343a
......@@ -11,9 +11,28 @@
* COMMENT To do items
** DONE Center institutions under authors
** TODO Finish "Future Directions"
** DONE Finish "Future Directions"
[[*Future directions]]
* Possible theme for enhancements section
A number of things (returning values, handling cross-system dependencies
properly) would be simplified if the ASDF plans were hierarchically (tree)
structured, instead of being just flat sequences.
Plans would have a flat, sequential form for execution, but there would be a
superstructure that could accumulate values, etc.
This would also help give operations on modules and systems a more intuitive
semantics.
Could also help let people write useful =:around= methods.
Question: could we weave this into the concluding part of the talk.
*POSSIBLY* --- propose not to do this unless it can be done reasonably clearly,
and there may not be enough time remaining.
* COMMENT Org-principles for this document
** Just like outline mode --- More "*" in header means deeper nesting
......@@ -201,6 +220,36 @@ sub-bullet under a major header.
loaded?
+ Systems and modules are not components like others
** Possible new features
*** More declarative =DEFSYSTEM=
**** Current procedural aspects make introspection difficult
**** Need procedural code to invoke ASDF extensions
**** Would require modifying how DEFSYSTEM is read
*** Make =TRAVERSE= part of the API
**** Pro: Would allow cleaner extensions
**** Con: Might lock in buggy behavior
*** Conditional components
**** E.g., only load this file if you are doing the =TEST-OP=
*** More operations (e.g., =DOC-OP=)
*** Return values
**** =OPERATE= doesn't return a value --- bad for, e.g., testing
**** Complicated by linear plans --- no hierarchical structure for collecting return values
*** COMMENT --- possible theme here --- having /hierarchical/ plans might make a lot of things easier.
* Conclusions
......@@ -249,6 +298,8 @@ sub-bullet under a major header.
******* Corman (no response)
***** COMMENT end of columns
*** =:asdf2= in =*features*=
** Conclusions
......
Markdown is supported
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