[Nice-commit] Nice/web manual.xml,1.29,1.30

[<bo...@us...>]

Update of /cvsroot/nice/Nice/web
In directory sc8-pr-cvs1:/tmp/cvs-serv24859/web

Modified Files:
	manual.xml 
Log Message:
Added for explanation about the utility of exact matching.

Restored a precision about method implementations and default values.


Index: manual.xml
===================================================================
RCS file: /cvsroot/nice/Nice/web/manual.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** manual.xml	17 Dec 2003 11:06:35 -0000	1.29
--- manual.xml	17 Dec 2003 11:53:59 -0000	1.30
***************
*** 432,436 ****
  
        <para>
!         There is an <link linkend="ex:copy">example</link> where 
  	exact matching is required to
  	type-check a method with a precise polymorphic type.
--- 432,442 ----
  
        <para>
!         Specializing on the exact class of an argument is useful in situations
! 	where an implementation is correct for a certain class, but you know
! 	that each subclass will require a different implementation.	
!       </para>
! 
!       <para>
!         There is also an <link linkend="ex:copy">example</link> where 
  	exact matching is required to
  	type-check a method with a precise polymorphic type.
***************
*** 479,483 ****
           Note that it is not possible to dispatch a method call on an array 
           type, nor to specialize a method on the subtype of a type parameter. 
!          This means that methods of the form:
          </para>
          <para>
--- 485,489 ----
           Note that it is not possible to dispatch a method call on an array 
           type, nor to specialize a method on the subtype of a type parameter. 
!          This means that method implementations of the form:
          </para>
          <para>
***************
*** 587,590 ****
--- 593,602 ----
         int to = array.length - 1);</literal>
        </para>
+ 
+       <para>
+         Method implementations must still bind all parameters,
+ 	including the optional ones, and can dispatch on them.
+       </para>
+ 
      </section>
    </chapter>