notation factored, coercion commant taking terms and not only URI

[helm.git] / helm / software / matita / help / C / sec_commands.xml

diff --git a/helm/software/matita/help/C/sec_commands.xml b/helm/software/matita/help/C/sec_commands.xml
index 5e55de9994648e7768358c6751f7eb2b96dbb589..4d788f39aa3feb8ed01961dd48a782b9ec2a6436 100644 (file)
--- a/helm/software/matita/help/C/sec_commands.xml
+++ b/helm/software/matita/help/C/sec_commands.xml
@@ -76,24 +76,34 @@
  </sect1>
  <sect1 id="command_coercion">
    <title>coercion</title>
-   <para><userinput>coercion u</userinput></para>
+   <para><userinput>coercion u with ariety saturation nocomposites</userinput></para>
    <para>
      <variablelist>
        <varlistentry>
          <term>Synopsis:</term>
          <listitem>
-           <para><emphasis role="bold">coercion</emphasis> &uri;</para>
+                <para>
+                        <emphasis role="bold">coercion</emphasis> 
+                        (&uri; | &term; <emphasis role="bold">with</emphasis>)
+                        [ &nat; [&nat;]] 
+                        [ <emphasis role="bold">nocomposites</emphasis> ]
+                </para>
          </listitem>
        </varlistentry>
        <varlistentry>
          <term>Action:</term>
          <listitem>
-           <para>Declares <command>u</command> as an implicit coercion
-            from the type of its last argument (source)
-            to its codomain (target). Every time a term <command>x</command>
+                <para>Declares <command>u</command> as an implicit coercion.
+                If the type of <command>u</command> is         
+                <command>∀x1:T1. … ∀x(n-1):T(n-1).Tn</command> the coercion target is
+                <command>T(n - ariety)</command> while its source is 
+                <command>T(n - ariety - saturation - 1)</command>.
+           Every time a term <command>x</command>
             of type source is used with expected type target, Matita
             automatically replaces <command>x</command> with
-            <command>(u ? … ? x)</command> to avoid a typing error.</para>
+            <command>(u ? … ? x ? … ?)</command> to avoid a typing error.</para>
+            Note that the number of <command>?</command> added after 
+           <command>x</command> is saturation.
            <para>Implicit coercions are not displayed to the user:
             <command>(u ? … ? x)</command> is rendered simply
             as <command>x</command>.</para>
@@ -102,7 +112,8 @@
             and there is already a coercion <command>u'</command> of
             target <command>s</command> or source <command>t</command>,
             a composite implicit coercion is automatically computed
-            by Matita.</para>
+           by Matita unless <emphasis role="bold">nocomposites</emphasis> 
+           is specified.</para>
          </listitem>
        </varlistentry>
      </variablelist>
@@ -254,8 +265,7 @@
             On the contrary, theorem and definitions declared in a file can be
            immediately used without including it.</para>
           <para>The file <command>s</command> is automatically compiled
-           if it is not compiled yet and if it is handled by a
-           <link linkend="developments">development</link>.
+         if it is not compiled yet.
           </para>
          </listitem>
        </varlistentry>
@@ -282,36 +292,6 @@
      </variablelist>
    </para>
  </sect1>
- <sect1 id="command_set">
-   <title>set</title>
-   <para><userinput>set &quot;baseuri&quot; &quot;s&quot;</userinput></para>
-   <para>
-     <variablelist>
-       <varlistentry>
-         <term>Synopsis:</term>
-         <listitem>
-           <para><emphasis role="bold">set</emphasis> &qstring; &qstring;</para>
-         </listitem>
-       </varlistentry>
-       <varlistentry>
-         <term>Action:</term>
-         <listitem>
-           <para>Sets to <command>s</command> the baseuri of all the
-            theorems and definitions stated in the current file.
-            The baseuri should be <command>a/b/c/foo</command>
-            if the file is named <command>foo</command> and it is in
-            the subtree <command>a/b/c</command> of the current
-            <link linkend="developments">development</link>.
-            This requirement is not enforced, but it could be in the future.
-           </para>
-           <para>Currently, <command>baseuri</command> is the only
-            property that can be set even if the parser accepts
-            arbitrary property names.</para>
-         </listitem>
-       </varlistentry>
-     </variablelist>
-   </para>
- </sect1>
  <sect1 id="command_whelp">
    <title>whelp</title>
    <para><userinput>whelp locate &quot;s&quot;</userinput></para>