Author: masak
Date: 2010-01-08 16:50:59 +0100 (Fri, 08 Jan 2010)
New Revision: 29480
Modified:
docs/Perl6/Spec/S12-objects.pod
docs/Perl6/Spec/S32-setting-library/Exception.pod
Log:
[S12-objects] various consistencifications
- one case of 'enum type' which should be 'enumeration type'
- the C<.true> method is now called C<.so>, according to S32
- so is the function
- s/an an/an/
[S32] removed comment about musings about .true and .defined
The musings are actually addressed in some of the above corrected
paragraphs in S12.
Modified: docs/Perl6/Spec/S12-objects.pod
===================================================================
--- docs/Perl6/Spec/S12-objects.pod 2010-01-08 07:34:08 UTC (rev 29479)
+++ docs/Perl6/Spec/S12-objects.pod 2010-01-08 15:50:59 UTC (rev 29480)
@@ -13,8 +13,8 @@
Created: 27 Oct 2004
- Last Modified: 3 Dec 2009
- Version: 95
+ Last Modified: 8 Jan 2010
+ Version: 96
=head1 Overview
@@ -1681,7 +1681,7 @@
The declared base type automatically distributes itself to the individual
constant values. For non-native types, the enum objects are guaranteed
only to be derived from and convertible to the specified type. The
-actual type of the enum object returned by using the symbol is the enum type
itself.
+actual type of the enum object returned by using the symbol is the enumeration
type itself.
Fri.WHAT # Day, not Int.
+Fri # 5
@@ -1691,8 +1691,8 @@
Fri.defined # True
Other than that, number valued enums act just like numbers, while
-string valued enums act just like strings. C<Fri.true> is true
-because its value is 5 rather than 0. C<Sun.true> is false.
+string valued enums act just like strings. C<Fri.so> is true
+because its value is 5 rather than 0. C<Sun.so> is false.
Enums based on native types may be used only for their value, since a
native value doesn't know its own type.
@@ -1807,7 +1807,7 @@
An enum type is not in itself a role type; however, the C<but>
and C<does> operators know that when a user supplies an enum type,
it implies the generation of an anonymous mixin role that creates an
-an appropriate accessor, read-write if an attribute is being created, and
+appropriate accessor, read-write if an attribute is being created, and
read-only otherwise. It depends on whether you mix in the whole
or a specific enum or the whole enumeration:
@@ -1913,11 +1913,11 @@
$obj.Bool != 0
-Never compare a value to "C<true>", or even "C<True>". Just use it
+Never compare a value to "C<so>", or "C<True>". Just use it
in a boolean context. Well, almost never...
If you wish to be explicit about a boolean context, use the high-level
-C<true> function or C<?> prefix operator, which are underlying based
+C<so> function or C<?> prefix operator, which are underlying based
on the C<.Bool> method. Also, use these high level functions when you wish
to autothread junctions, since C<.Bool> forces collapse of a junction's
wavefunction. (Similarly, C<.Str> forces stringification of the entire
junction,
Modified: docs/Perl6/Spec/S32-setting-library/Exception.pod
===================================================================
--- docs/Perl6/Spec/S32-setting-library/Exception.pod 2010-01-08 07:34:08 UTC
(rev 29479)
+++ docs/Perl6/Spec/S32-setting-library/Exception.pod 2010-01-08 15:50:59 UTC
(rev 29480)
@@ -14,8 +14,8 @@
Created: 26 Feb 2009
- Last Modified: 26 Feb 2009
- Version: 1
+ Last Modified: 8 Jan 2010
+ Version: 2
The document is a draft.
@@ -34,7 +34,7 @@
}
role Failure {
- method Bool {...} # XXX I'm hoping this worries about .defined and
.true
+ method Bool {...}
method handled {...}
}
