Skip to content

Commit 4217af7

Browse files
Fixed bad URL (#2333)
1 parent ca7cb59 commit 4217af7

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/Type/Signature.pod6

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -395,18 +395,18 @@ be confusing, since the terms have subtly different meanings.
395395
396396
As explained above, I<definiteness> is concerned with the distinction between
397397
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
399399
object/indefinite or an object instance/definite can be verified using the
400400
L<DEFINITE|/language/mop#DEFINITE> (meta)method.
401401
402402
I<Definiteness> should be distinghuished from I<definedness>, which is concerned
403403
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
405405
implemented in class L<Mu|/type/Mu>. By default a type object is considered
406406
undefined, while an object instance is considered defined; that is: C<.defined>
407407
returns C<False> on a type object, and C<True> otherwise. But this default
408408
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>,
410410
so that even an instantiated C<Failure> acts as an undefined value:
411411
412412
my $a = Failure; # Initialize with type object

0 commit comments

Comments
 (0)