Author: lwall
Date: 2009-08-31 21:56:55 +0200 (Mon, 31 Aug 2009)
New Revision: 28146

Modified:
   docs/Perl6/Spec/S02-bits.pod
Log:
[S02] remove fossil noticed by pmichaud++


Modified: docs/Perl6/Spec/S02-bits.pod
===================================================================
--- docs/Perl6/Spec/S02-bits.pod        2009-08-31 19:55:44 UTC (rev 28145)
+++ docs/Perl6/Spec/S02-bits.pod        2009-08-31 19:56:55 UTC (rev 28146)
@@ -13,8 +13,8 @@
 
     Created: 10 Aug 2004
 
-    Last Modified: 24 Aug 2009
-    Version: 174
+    Last Modified: 31 Aug 2009
+    Version: 175
 
 This document summarizes Apocalypse 2, which covers small-scale
 lexical items and typological issues.  (These Synopses also contain
@@ -633,10 +633,11 @@
 is not required to unless we can do so portably and efficiently.  C<Num>
 must support the largest native floating point format that runs at full speed.)
 
-C<Rat> supports arbitrary precision rational arithmetic.  However,
-dividing two C<Int> objects using C<< infix:</> >> produces a
-fraction of C<Num> type, not a ratio.  You can produce a ratio by
-using C<< infix:<div> >> on two integers instead.
+C<Rat> supports arbitrary precision rational arithmetic.
+Dividing two C<Int> objects using C<< infix:</> >> produces a
+a C<Rat>, which is generally usable anywhere a C<Num> is usable, but
+may also be explicitly cast to C<Num>.  (Also, if either side is
+C<Num> already, C<< infix:</> >> gives you a C<Num> instead of a C<Rat>.)
 
 Lower-case types like C<int> and C<num> imply the native
 machine representation for integers and floating-point numbers,

Reply via email to