diff options
author | David Aspinall <da@inf.ed.ac.uk> | 2000-03-08 05:57:50 +0000 |
---|---|---|
committer | David Aspinall <da@inf.ed.ac.uk> | 2000-03-08 05:57:50 +0000 |
commit | 214f1da42a3669caec9864a516f3697f5e8deef6 (patch) | |
tree | 79925ce509c84b25cd14eafd49262dbcb40aba22 /lego | |
parent | 9d83ebfc4d9840f5e6634cac2145ed7d6a92d406 (diff) |
Split low-level todo into several files.
Diffstat (limited to 'lego')
-rw-r--r-- | lego/todo | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/lego/todo b/lego/todo new file mode 100644 index 00000000..99a8154e --- /dev/null +++ b/lego/todo @@ -0,0 +1,45 @@ +-*- mode:outline -*- + +* See also ../todo for generic things to do, priority codes. + +* Things to do for Lego +======================= + +C Improve X-Symbol support. + +D Fix Pbp implementation in LEGO itself (10h) + +D In LEGO, apart from Goal...Save pairs, we have + declaration...discharge pairs. See the section "Granularity of + Atomic Commands" for a proposal on how to generalise the current + implementation so that it can also deal with "Discharge". + [See also the Coq problem with Sections] (6h) + +D Inoking an "Expand" command produces a new proof state. But this is + incorrectly displayed in the response buffer and not the goals + buffer because special annotations are missing. Presumably, one + ought to replace "Toplevel.Pr()" by "Toplevel.PR()" in the + definition of "Expand" (see file newtop.sml [Version 1.4]). (30min) + +D Even with the more flexible region model, with + proof-nested-goals-behaviour=closequick, Proof General doesn't + do quite the right thing. Forget for a definition when inside + a proofstate kills off the whole proofstate. Effectively, + the definition is *global* rather than local to the proofstate, + and could perhaps be lifted to before the goal + (with the lift-global nonsense not so daft after all? Editing + behind the user's back is still objectionable though). + Another alternative fix would be to trigger some retraction action + on seeing the "Abort" regexp, rather than assuming it is the result of + some retraction action. More generally this could be used for error + handling. + +D Improve legotags. It cannot handle lists e.g., with + [x,y:nat]; + it only tags x but not y. [The same problem exists for coqtags] + +X Mechanism to save object file. Specifically, after having processed + a script (interactively), it would be nice if one could now save the + buffer in object format. At the moment, it only gets converted + (automatically) when it is read in indirectly at a later stage. + However, there is currently no LEGO command to do this. [4h] |