X-Git-Url: http://matita.cs.unibo.it/gitweb/?a=blobdiff_plain;f=helm%2Fsoftware%2Fmatita%2Fhelp%2FC%2Fsec_commands.xml;h=4d788f39aa3feb8ed01961dd48a782b9ec2a6436;hb=ca41435a6021292ccba239aa173651c0be705b45;hp=5e55de9994648e7768358c6751f7eb2b96dbb589;hpb=b3488620204bbc7ea656c45096a703ff15160bd5;p=helm.git diff --git a/helm/software/matita/help/C/sec_commands.xml b/helm/software/matita/help/C/sec_commands.xml index 5e55de999..4d788f39a 100644 --- a/helm/software/matita/help/C/sec_commands.xml +++ b/helm/software/matita/help/C/sec_commands.xml @@ -76,24 +76,34 @@ coercion - coercion u + coercion u with ariety saturation nocomposites Synopsis: - coercion &uri; + + coercion + (&uri; | &term; with) + [ &nat; [&nat;]] + [ nocomposites ] + Action: - Declares u as an implicit coercion - from the type of its last argument (source) - to its codomain (target). Every time a term x + Declares u as an implicit coercion. + If the type of u is + ∀x1:T1. … ∀x(n-1):T(n-1).Tn the coercion target is + T(n - ariety) while its source is + T(n - ariety - saturation - 1). + Every time a term x of type source is used with expected type target, Matita automatically replaces x with - (u ? … ? x) to avoid a typing error. + (u ? … ? x ? … ?) to avoid a typing error. + Note that the number of ? added after + x is saturation. Implicit coercions are not displayed to the user: (u ? … ? x) is rendered simply as x. @@ -102,7 +112,8 @@ and there is already a coercion u' of target s or source t, a composite implicit coercion is automatically computed - by Matita. + by Matita unless nocomposites + is specified. @@ -254,8 +265,7 @@ On the contrary, theorem and definitions declared in a file can be immediately used without including it. The file s is automatically compiled - if it is not compiled yet and if it is handled by a - development. + if it is not compiled yet. @@ -282,36 +292,6 @@ - - set - set "baseuri" "s" - - - - Synopsis: - - set &qstring; &qstring; - - - - Action: - - Sets to s the baseuri of all the - theorems and definitions stated in the current file. - The baseuri should be a/b/c/foo - if the file is named foo and it is in - the subtree a/b/c of the current - development. - This requirement is not enforced, but it could be in the future. - - Currently, baseuri is the only - property that can be set even if the parser accepts - arbitrary property names. - - - - - whelp whelp locate "s"