@@ -395,18 +395,18 @@ be confusing, since the terms have subtly different meanings.
395
395
396
396
As explained above, I < definiteness > is concerned with the distinction between
397
397
type objects and object instances. A type object is always indefinite, while an
398
- object instance is always definite. Whether or not an object is a type
398
+ object instance is always definite. Whether an object is a type
399
399
object/indefinite or an object instance/definite can be verified using the
400
400
L < DEFINITE|/language/mop#DEFINITE > (meta)method.
401
401
402
402
I < Definiteness > should be distinghuished from I < definedness > , which is concerned
403
403
with the difference between defined and undefined objects. Whether an object is
404
- defined or undefined can be verified using the C < . defined> -method, which is
404
+ defined or undefined can be verified using the C < defined > -method, which is
405
405
implemented in class L < Mu|/type/Mu > . By default a type object is considered
406
406
undefined, while an object instance is considered defined; that is: C < .defined >
407
407
returns C < False > on a type object, and C < True > otherwise. But this default
408
408
behaviour may be overridden by subclasses. An example of a subclass that
409
- overrides the default C < .defined > behaviour is L < Failure|type/Failure > ,
409
+ overrides the default C < .defined > behaviour is L < Failure|/ type/Failure > ,
410
410
so that even an instantiated C < Failure > acts as an undefined value:
411
411
412
412
my $a = Failure; # Initialize with type object
0 commit comments