1 * MW: clarify/eliminate Isabelle/Scala add-ons (presently unused)
3 diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/build-jars ./src/Pure/build-jars
5 > src/Tools/isac/BridgeJEdit/isac.scala
7 diff -r /home/makarius/isabelle/repos-Isabelle2021/src/Pure/Tools/scala_project.scala ./src/Pure/Tools/scala_project.scala
9 > "src/Tools/isac/etc" -> Path.explode("isabelle.isac"),
11 * MW: Skip_Proof.make_thm: theory -> term -> thm ? could now change signature to
12 : Proof.context -> term -> thm
13 * How does declare [[LI_trace = true]] and declare [[rewrite_trace = true]] work in ISABELLE_ISAC_TEST ?
17 ***** some items for discussion
19 * Clarify symmetric rule: Thm.apply_attribute Calculation.symmetric thm context (!?);
22 * "fun pr_ord" is not required if used with @{make_string}, @{print}, @{print tracing};
23 takes only static arguments ----------------^^^^^^^^^^^^^^, not value of "hd_ord (f, g)"
24 ? are there better approximations to old output of (*1*) than with (*2*)
25 (*1*)val _ = tracing ("hd_ord (f, g) = " ^ ((pr_ord o hd_ord) (f, g)) );
26 (*2*)val _ = @{print tracing}{a = "hd_ord (f, g) = ", z = hd_ord (f, g)}(**)
29 ***** for the few items below WN asks MW for help
31 * MW: make Outer_Syntax.command..‹problem› a model for ..\<open>Example\<close>
32 The model should demonstrate, how an ML syntax error is indicated in place
33 (in the string after \<^keyword>\<open>Given\<close> etc) and not on the definition as a whole.
34 - in MathEngBasic/problem "Outer_Syntax.command \<^command_keyword>\<open>problem\<close>" there are writeln
35 and comments with testdata from "problem pbl_bieg : "Biegelinien"" in Biegelinie.thy
36 - in MathEngBasic/problem there is guesswork ("TODO") how to reorganise "fun prep_input"
37 such that errors in "Given" etc are indicated WITHIN the term.
39 * MW: In Outer_Syntax.command..‹Example› help: is there a quick fix
40 for successfully replacing hacked Problem.parse_cas by parse_references_input?
41 (a) In addition to replacing Problem.parse_cas: How implement the optional parser:
42 - Example "Diff_App/No.123 a" + NONE
43 - Example "Diff_App/No.123 a" + SOME (probl_id, model_input, refs_input)
44 i.e. we expect ISAC to present an empty template "Problem..Solution", but as a whole, to the user;
45 see VSCode_Example.thy subsubsection \<open>Specification step by step\<close>
46 How get Token.src for testing purposes?
47 How can Scan.* be traced?
48 (Tracing should help understanding Problem.parse_cas, Problem.parse_model_input which involve Scan.* )
50 * ?How represent items, which have not yet been input?
51 Note: For the purpose of user-guidance the format of requested input should be indicated!
52 - proposal for how to indicate requested input: in VSCode_Example.thy subsubsection \<open>Empty Specification>
53 - the trial with <fun is_empty> in Calculation.thy makes the question more precise:
54 better hack parsers or better work on ML_Syntax?
56 * ?How accomplish two user-requirements by Outer_Syntax.command \<^command_keyword>\<open>Example\<close>
57 (1) start a Calculation with a CAS_Cmd
58 (2) start an Example from scratch, i.e. with (Formalize.empty, References.empty)
59 Proposals for a solution are in test/../Test_VSCode_Example.thy
60 subsubsection ‹Start Example with a CAS_Cmd›
63 ***** priority of WN items is top down, most urgent/simple on top
65 * WN: follow up 5d: clarify TermC.parse_patt/*_PIDE analogous to TermC.parse_strict/*_PIDE
66 follow up 6: ctxt_user at init Example mimiced by CalcTreeTest @{context}
67 Thus eliminate use of Thy_Info.get_theory
68 follow up 7: ANSWER: represent items, which have not yet been input IN VSCode_Example.thy WITH "__"
70 * WN: improve naming in refine.sml, m-match.sml
71 * WN: rename ‹ML_structure KEStore_Elems› to ‹ML_structure Know_Store›
72 * WN: KEStore_Elems.get_thes, add_thes still required for Error_Patterns, we want to eliminate thes:
73 (1) Error_Pattern.T are already stored by MethodC -- place them in respective thys
74 (2) Error_Pattern.fill_in stored with thm (in thes): instead introduce new Thy_Data for them.
75 adapt KEStore_Elems.insert_fillpats for that purpose.
77 * WN: Specify/formalise.sml is in BaseDefinitions/ AND Specify/ DELETE ONE VERSION
78 * WN: Step_Specify.initialise: remove hdl in return-value, replace Step_Specify.nxt_specify_init_calc
79 ? which uses initialise !?
80 * WN: ? unify "no_met" with "empty_meth_id" from References.empty ?
82 * WN: proper ML antiquotations for "Tactical.Try" etc. --- be careful about unclear situations,
83 e.g. "Tactical.Try" vs. "Lucas_Interpreter.Try";
85 * WN: ? Rational.Cancel_p; extend use of \<^theory> to \<^theory_context>
87 * WN: Avoid Thm.get_name_hint and use Global_Theory.get_thm instead, get theory from References.T
88 and push theory through as argument of respective functions.
90 * WN: Eliminate Thy_Info.get_theory eventually: should take theory from ancestory
91 within current context.
92 cf. e587c45cae0f note in Build_Thydata.thy
94 * WN: Check/clarify Context.theory_name vs. Context.theory_long_name.
95 present ISAC assumes 2 sessions in the MathEngine, Specify and Interpret,
96 and all Isac_Knowledge is in session Isac.
97 So Context.theory_name suffices
99 * WN: more direct logical foundations wrt. Isabelle/HOL, eliminate many axiomatizations
100 - quite often "axiomatization ..." can be turned into "lemma ... by auto"
102 - sometimes this requires to use more specific types / type classes;
103 - sometimes this requires to use proper definitional mechanisms (e.g. 'primrec', 'fun');
104 - a few "hard" cases will remain, to be reconsidered eventually (e.g. differentiation);
106 * WN: eliminate argument theory from Interpret/*, e.g. (LI_Tool.tac_from_prog + see TODO.thy)
107 * WN: rename Pos.* -- Pos.ints, Pos.spec, Pos.empty, Pos.ints_empty
109 * WN: redesign transition from Specification to Solution: how relate
110 - Formalise.model with variants (e.g. VSCode_Example)
111 reconsider separation of variants F_I, F_II, see MAWEN paper
112 - !?! I_Model of MethodC (fairly free sequence, dependent on Formalise.model)
113 - !?! formal arguments of program (fixed sequence)