Walther@60484
|
1 |
* MW: make Outer_Syntax.command \<^command_keyword>\<open>problem\<close> a model for ..\<open>Example\<close>
|
Walther@60484
|
2 |
An ML syntax error should be indicated in place (in the string after \<^keyword>\<open>Given\<close> etc)
|
Walther@60484
|
3 |
and not on the definition as a whole.
|
Walther@60487
|
4 |
- in MathEngBasic/problem "Outer_Syntax.command \<^command_keyword>\<open>problem\<close>" there are writeln
|
Walther@60487
|
5 |
and comments with testdata from "problem pbl_bieg : "Biegelinien"" in Biegelinie.thy
|
Walther@60487
|
6 |
- in MathEngBasic/problem there is guesswork ("TODO") how to reorganise "fun prep_input_PIDE"
|
Walther@60487
|
7 |
such that errors in "Given" etc are indicated WITHIN the term.
|
Walther@60484
|
8 |
|
Walther@60485
|
9 |
* ?MW?: In Outer_Syntax.command \<^command_keyword>\<open>Example\<close> is there a quick fix
|
Walther@60485
|
10 |
for successfully replacing hacked Problem.parse_cas by parse_references_input?
|
Walther@60492
|
11 |
(a) In addition to replacing Problem.parse_cas: How implement the optional parser:
|
Walther@60492
|
12 |
- Example "Diff_App/No.123 a" + NONE
|
Walther@60492
|
13 |
- Example "Diff_App/No.123 a" + SOME (probl_id, model_input, refs_input)
|
Walther@60492
|
14 |
i.e. we expect ISAC to present an empty template "Problem..Solution", but as a whole, to the user;
|
Walther@60492
|
15 |
see VSCode_Example.thy subsubsection \<open>Specification step by step\<close>
|
Walther@60487
|
16 |
How get Token.src for testing purposes?
|
Walther@60485
|
17 |
How can Scan.* be traced?
|
Walther@60485
|
18 |
(Tracing should help understanding Problem.parse_cas, Problem.parse_model_input which involve Scan.*)
|
Walther@60485
|
19 |
|
wenzelm@60234
|
20 |
* MW: check uses of Unsynchronized.ref vs. Synchronized.var;
|
wenzelm@60234
|
21 |
|
wenzelm@60216
|
22 |
* MW: clarify/eliminate Isabelle/Scala add-ons (presently unused)
|
wenzelm@60216
|
23 |
|
wenzelm@60216
|
24 |
diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/build-jars ./src/Pure/build-jars
|
wenzelm@60216
|
25 |
11a12
|
wenzelm@60216
|
26 |
> src/Tools/isac/BridgeJEdit/isac.scala
|
wenzelm@60216
|
27 |
|
wenzelm@60216
|
28 |
diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/Tools/scala_project.scala ./src/Pure/Tools/scala_project.scala
|
wenzelm@60216
|
29 |
76a77
|
wenzelm@60216
|
30 |
> "src/Tools/isac/etc" -> Path.explode("isabelle.isac"),
|
wenzelm@60225
|
31 |
|
wenzelm@60316
|
32 |
* Eliminate Thy_Info.get_theory eventually: should take theory from ancestory
|
walther@60363
|
33 |
within current context.
|
walther@60362
|
34 |
cf. e587c45cae0f note in Build_Thydata.thy
|
wenzelm@60316
|
35 |
|
wenzelm@60295
|
36 |
* Clarify symmetric rule: Thm.apply_attribute Calculation.symmetric thm context (!?);
|
walther@60369
|
37 |
??
|
wenzelm@60295
|
38 |
|
wenzelm@60316
|
39 |
* KEStore_Elems: Should we eliminate union_overwrite and use standard namespace merge?
|
wenzelm@60316
|
40 |
(Exception: rlss with its special cross-theory merge.)
|
walther@60376
|
41 |
? how adapt the different signatures ?
|
walther@60376
|
42 |
union_overwrite: ('a * 'a -> bool) -> 'a list -> 'a list -> 'a list
|
walther@60376
|
43 |
merge : ('a * 'a -> bool) -> 'a list * 'a list -> 'a list
|
wenzelm@60285
|
44 |
|
wenzelm@60281
|
45 |
* What is the purpose of "#numeral" instead of plain numeral?
|
walther@60368
|
46 |
??
|
wenzelm@60281
|
47 |
|
wenzelm@60281
|
48 |
* Check/clarify Context.theory_name vs. Context.theory_long_name.
|
walther@60369
|
49 |
present ISAC assumes 2 sessions in the MathEngine, Specify and Interpret,
|
walther@60369
|
50 |
and all Isac_Knowledge is in session Isac.
|
walther@60369
|
51 |
So Context.theory_name suffices
|
wenzelm@60281
|
52 |
|
wenzelm@60292
|
53 |
* Eliminate mutable Rewrite_Ord.rew_ord' (!?);
|
walther@60362
|
54 |
shall be done in connection with cf. e587c45cae0f note in Build_Thydata.thy
|
wenzelm@60292
|
55 |
|
wenzelm@60315
|
56 |
* What is the idea behind KEStore_Elems.add_thes? How to do it properly in current Isabelle?
|
walther@60365
|
57 |
https://static.miraheze.org/isacwiki/0/04/Isac-docu.pdf distinguishes
|
walther@60365
|
58 |
several kinds of ISAC users, in particular "math author (Mathematik-Autor)" and
|
walther@60365
|
59 |
"course designer (Kurs-Designer)". The latter just adds examples which re-use existing
|
walther@60365
|
60 |
knowledge designed by the former. KEStore_Elems.add_thes is an interface for the latter.
|
wenzelm@60315
|
61 |
|
wenzelm@60311
|
62 |
* WN: proper ML antiquotations for "Tactical.Try" etc. --- be careful about unclear situations,
|
wenzelm@60311
|
63 |
e.g. "Tactical.Try" vs. "Lucas_Interpreter.Try";
|
wenzelm@60311
|
64 |
|
walther@60376
|
65 |
* WN: Avoid Thm.get_name_hint and use Global_Theory.get_thm instead, get theory from References.T
|
walther@60370
|
66 |
and push theory through as argument of respective functions.
|
wenzelm@60304
|
67 |
|
wenzelm@60241
|
68 |
* WN: more direct logical foundations wrt. Isabelle/HOL, eliminate many axiomatizations
|
wenzelm@60241
|
69 |
- quite often "axiomatization ..." can be turned into "lemma ... by auto"
|
wenzelm@60241
|
70 |
without further ado;
|
wenzelm@60241
|
71 |
- sometimes this requires to use more specific types / type classes;
|
wenzelm@60241
|
72 |
- sometimes this requires to use proper definitional mechanisms (e.g. 'primrec', 'fun');
|
wenzelm@60241
|
73 |
- a few "hard" cases will remain, to be reconsidered eventually (e.g. differentiation);
|
wenzelm@60234
|
74 |
|
wenzelm@60247
|
75 |
* WN: "fun pr_ord" is not required if used with @{make_string}, @{print}, @{print tracing};
|
walther@60375
|
76 |
takes only static arguments ----------------^^^^^^^^^^^^^^, not value of "hd_ord (f, g)"
|
walther@60375
|
77 |
? are there better approximations to old output of (*1*) than with (*2*)
|
walther@60375
|
78 |
(*1*)val _ = tracing ("hd_ord (f, g) = " ^ ((pr_ord o hd_ord) (f, g)) );
|
walther@60375
|
79 |
(*2*)val _ = @{print tracing}{a = "hd_ord (f, g) = ", z = hd_ord (f, g)}(**)
|
walther@60317
|
80 |
|
wenzelm@60379
|
81 |
|
wenzelm@60379
|
82 |
* WN: eliminate global flags like "trace_on", replace Unsynchronized.ref by
|
wenzelm@60379
|
83 |
|
wenzelm@60379
|
84 |
ML \<open>
|
wenzelm@60379
|
85 |
val rewrite_trace = Attrib.setup_config_bool \<^binding>\<open>rewrite_trace\<close> (K false);
|
wenzelm@60379
|
86 |
\<close>
|
Walther@60434
|
87 |
|
Walther@60466
|
88 |
* WN: redesign transition from Specification to Solution: how relate
|
Walther@60466
|
89 |
- Formalise.model with variants (e.g. VSCode_Example)
|
Walther@60466
|
90 |
reconsider separation of variants F_I, F_II, see MAWEN paper
|
Walther@60466
|
91 |
- !?! I_Model of MethodC (fairly free sequence, dependent on Formalise.model)
|
Walther@60466
|
92 |
- !?! formal arguments of program (fixed sequence)
|
Walther@60437
|
93 |
|
Walther@60492
|
94 |
* WN: ?How represent items, which have not yet been input?
|
Walther@60492
|
95 |
Note: For the purpose of user-guidance the format of requested input should be indicated!
|
Walther@60492
|
96 |
- proposal for how to indicate requested input: in VSCode_Example.thy subsubsection \<open>Empty Specification>
|
Walther@60499
|
97 |
- the trial with <fun is_empty> in Calculation.thy makes the question more precise:
|
Walther@60499
|
98 |
better hack parsers or better work on ML_Syntax?
|
Walther@60492
|
99 |
|
Walther@60493
|
100 |
* WN: as soon as parsing in Outer_Syntax.command..‹Example› works, implement in Calculation
|
Walther@60493
|
101 |
- init_ctree, update_status, check_input
|
Walther@60492
|
102 |
|
Walther@60493
|
103 |
|