wenzelm@60216
|
1 |
* MW: clarify/eliminate Isabelle/Scala add-ons (presently unused)
|
wenzelm@60216
|
2 |
|
wenzelm@60216
|
3 |
diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/build-jars ./src/Pure/build-jars
|
wenzelm@60216
|
4 |
11a12
|
wenzelm@60216
|
5 |
> src/Tools/isac/BridgeJEdit/isac.scala
|
wenzelm@60216
|
6 |
|
wenzelm@60216
|
7 |
diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/Tools/scala_project.scala ./src/Pure/Tools/scala_project.scala
|
wenzelm@60216
|
8 |
76a77
|
wenzelm@60216
|
9 |
> "src/Tools/isac/etc" -> Path.explode("isabelle.isac"),
|
wenzelm@60225
|
10 |
|
Walther@60519
|
11 |
* MW: Skip_Proof.make_thm: theory -> term -> thm ? could now change signature to
|
Walther@60519
|
12 |
: Proof.context -> term -> thm
|
Walther@60556
|
13 |
* How does declare [[LI_trace = true]] and declare [[rewrite_trace = true]] work in ISABELLE_ISAC_TEST ?
|
Walther@60556
|
14 |
|
Walther@60519
|
15 |
|
Walther@60512
|
16 |
|
Walther@60512
|
17 |
***** some items for discussion
|
Walther@60512
|
18 |
|
wenzelm@60295
|
19 |
* Clarify symmetric rule: Thm.apply_attribute Calculation.symmetric thm context (!?);
|
walther@60369
|
20 |
??
|
wenzelm@60295
|
21 |
|
Walther@60512
|
22 |
* "fun pr_ord" is not required if used with @{make_string}, @{print}, @{print tracing};
|
Walther@60512
|
23 |
takes only static arguments ----------------^^^^^^^^^^^^^^, not value of "hd_ord (f, g)"
|
Walther@60512
|
24 |
? are there better approximations to old output of (*1*) than with (*2*)
|
Walther@60512
|
25 |
(*1*)val _ = tracing ("hd_ord (f, g) = " ^ ((pr_ord o hd_ord) (f, g)) );
|
Walther@60512
|
26 |
(*2*)val _ = @{print tracing}{a = "hd_ord (f, g) = ", z = hd_ord (f, g)}(**)
|
Walther@60512
|
27 |
|
wenzelm@60281
|
28 |
|
Walther@60512
|
29 |
***** for the few items below WN asks MW for help
|
wenzelm@60281
|
30 |
|
Walther@60552
|
31 |
* MW: make Outer_Syntax.command..‹problem› a model for ..\<open>Example\<close>
|
Walther@60512
|
32 |
The model should demonstrate, how an ML syntax error is indicated in place
|
Walther@60512
|
33 |
(in the string after \<^keyword>\<open>Given\<close> etc) and not on the definition as a whole.
|
Walther@60512
|
34 |
- in MathEngBasic/problem "Outer_Syntax.command \<^command_keyword>\<open>problem\<close>" there are writeln
|
Walther@60512
|
35 |
and comments with testdata from "problem pbl_bieg : "Biegelinien"" in Biegelinie.thy
|
Walther@60512
|
36 |
- in MathEngBasic/problem there is guesswork ("TODO") how to reorganise "fun prep_input_PIDE"
|
Walther@60512
|
37 |
such that errors in "Given" etc are indicated WITHIN the term.
|
wenzelm@60292
|
38 |
|
Walther@60552
|
39 |
* MW: In Outer_Syntax.command..‹Example› help: is there a quick fix
|
Walther@60512
|
40 |
for successfully replacing hacked Problem.parse_cas by parse_references_input?
|
Walther@60512
|
41 |
(a) In addition to replacing Problem.parse_cas: How implement the optional parser:
|
Walther@60512
|
42 |
- Example "Diff_App/No.123 a" + NONE
|
Walther@60512
|
43 |
- Example "Diff_App/No.123 a" + SOME (probl_id, model_input, refs_input)
|
Walther@60512
|
44 |
i.e. we expect ISAC to present an empty template "Problem..Solution", but as a whole, to the user;
|
Walther@60512
|
45 |
see VSCode_Example.thy subsubsection \<open>Specification step by step\<close>
|
Walther@60512
|
46 |
How get Token.src for testing purposes?
|
Walther@60512
|
47 |
How can Scan.* be traced?
|
Walther@60512
|
48 |
(Tracing should help understanding Problem.parse_cas, Problem.parse_model_input which involve Scan.* )
|
wenzelm@60315
|
49 |
|
Walther@60512
|
50 |
* ?How represent items, which have not yet been input?
|
Walther@60512
|
51 |
Note: For the purpose of user-guidance the format of requested input should be indicated!
|
Walther@60512
|
52 |
- proposal for how to indicate requested input: in VSCode_Example.thy subsubsection \<open>Empty Specification>
|
Walther@60512
|
53 |
- the trial with <fun is_empty> in Calculation.thy makes the question more precise:
|
Walther@60512
|
54 |
better hack parsers or better work on ML_Syntax?
|
wenzelm@60311
|
55 |
|
Walther@60533
|
56 |
* ?How accomplish two user-requirements by Outer_Syntax.command \<^command_keyword>\<open>Example\<close>
|
Walther@60533
|
57 |
(1) start a Calculation with a CAS_Cmd
|
Walther@60533
|
58 |
(2) start an Example from scratch, i.e. with (Formalize.empty, References.empty)
|
Walther@60533
|
59 |
Proposals for a solution are in test/../Test_VSCode_Example.thy
|
Walther@60533
|
60 |
subsubsection ‹Start Example with a CAS_Cmd›
|
Walther@60533
|
61 |
|
wenzelm@60304
|
62 |
|
Walther@60512
|
63 |
***** priority of WN items is top down, most urgent/simple on top
|
wenzelm@60234
|
64 |
|
Walther@60557
|
65 |
* WN: follow up 5: cleanup
|
Walther@60556
|
66 |
follow up 6: ctxt_user at init Example mimiced by CalcTreeTest @{context}
|
Walther@60556
|
67 |
Thus eliminate use of Thy_Info.get_theory
|
Walther@60556
|
68 |
follow up 7: ANSWER ?How represent items, which have not yet been input? IN VSCode_Example.thy WITH "__"
|
Walther@60554
|
69 |
|
Walther@60556
|
70 |
* WN: improve naming in refine.sml, m-match.sml
|
Walther@60556
|
71 |
* WN: rename ‹ML_structure KEStore_Elems› to ‹ML_structure Know_Store›
|
Walther@60554
|
72 |
* WN: eliminate KEStore_Elems.get_thes, add_thes
|
Walther@60522
|
73 |
* What is the idea behind KEStore_Elems.add_thes? How to do it properly in current Isabelle?
|
Walther@60542
|
74 |
See notes in Build_Thydata.thy.
|
Walther@60522
|
75 |
https://static.miraheze.org/isacwiki/0/04/Isac-docu.pdf distinguishes
|
Walther@60522
|
76 |
several kinds of ISAC users, in particular "math author (Mathematik-Autor)" and
|
Walther@60522
|
77 |
"course designer (Kurs-Designer)". The latter just adds examples which re-use existing
|
Walther@60522
|
78 |
knowledge designed by the former. KEStore_Elems.add_thes is an interface for the latter.
|
Walther@60522
|
79 |
KEStore_Elems.get_thes and KEStore_Elems.add_thes are ONLY required for the Lucas-Interpreter
|
Walther@60522
|
80 |
retrieving Thm and Rls from string-identifiers (which do NOT indicate the theory of) --
|
Walther@60522
|
81 |
-- get_thes and add_thes are the main reason for (b)
|
Walther@60522
|
82 |
So: How can KEStore_Elems.get_thes and KEStore_Elems.add_thes be replaced in current Isabelle?
|
Walther@60500
|
83 |
|
Walther@60554
|
84 |
* WN: Specify/formalise.sml is in BaseDefinitions/ AND Specify/ DELETE ONE VERSION
|
Walther@60553
|
85 |
* WN: Step_Specify.initialise_PIDE: remove hdl in return-value, replace Step_Specify.nxt_specify_init_calc
|
Walther@60553
|
86 |
? which uses initialise_PIDE !?
|
Walther@60547
|
87 |
* WN: ? unify "no_met" with "empty_meth_id" from References.empty ?
|
Walther@60547
|
88 |
|
Walther@60512
|
89 |
* WN: proper ML antiquotations for "Tactical.Try" etc. --- be careful about unclear situations,
|
Walther@60512
|
90 |
e.g. "Tactical.Try" vs. "Lucas_Interpreter.Try";
|
Walther@60512
|
91 |
|
Walther@60500
|
92 |
* WN: ? Rational.Cancel_p; extend use of \<^theory> to \<^theory_context>
|
Walther@60500
|
93 |
|
Walther@60512
|
94 |
* WN: Avoid Thm.get_name_hint and use Global_Theory.get_thm instead, get theory from References.T
|
Walther@60512
|
95 |
and push theory through as argument of respective functions.
|
Walther@60512
|
96 |
|
Walther@60512
|
97 |
* WN: Eliminate Thy_Info.get_theory eventually: should take theory from ancestory
|
Walther@60512
|
98 |
within current context.
|
Walther@60512
|
99 |
cf. e587c45cae0f note in Build_Thydata.thy
|
Walther@60512
|
100 |
|
Walther@60512
|
101 |
* WN: Check/clarify Context.theory_name vs. Context.theory_long_name.
|
Walther@60512
|
102 |
present ISAC assumes 2 sessions in the MathEngine, Specify and Interpret,
|
Walther@60512
|
103 |
and all Isac_Knowledge is in session Isac.
|
Walther@60512
|
104 |
So Context.theory_name suffices
|
Walther@60512
|
105 |
|
Walther@60512
|
106 |
* WN: more direct logical foundations wrt. Isabelle/HOL, eliminate many axiomatizations
|
Walther@60512
|
107 |
- quite often "axiomatization ..." can be turned into "lemma ... by auto"
|
Walther@60512
|
108 |
without further ado;
|
Walther@60512
|
109 |
- sometimes this requires to use more specific types / type classes;
|
Walther@60512
|
110 |
- sometimes this requires to use proper definitional mechanisms (e.g. 'primrec', 'fun');
|
Walther@60512
|
111 |
- a few "hard" cases will remain, to be reconsidered eventually (e.g. differentiation);
|
Walther@60512
|
112 |
|
Walther@60534
|
113 |
* WN: eliminate argument theory from Interpret/*, e.g. (LI_Tool.tac_from_prog + see TODO.thy)
|
Walther@60520
|
114 |
* WN: rename Pos.* -- Pos.ints, Pos.spec, Pos.empty, Pos.ints_empty
|
Walther@60520
|
115 |
|
Walther@60466
|
116 |
* WN: redesign transition from Specification to Solution: how relate
|
Walther@60466
|
117 |
- Formalise.model with variants (e.g. VSCode_Example)
|
Walther@60466
|
118 |
reconsider separation of variants F_I, F_II, see MAWEN paper
|
Walther@60466
|
119 |
- !?! I_Model of MethodC (fairly free sequence, dependent on Formalise.model)
|
Walther@60466
|
120 |
- !?! formal arguments of program (fixed sequence)
|