Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[S02] unconfuse wording about type objects
since a type object is the opposite of an instance, it is confusing to call
it an instance of soemthing. anant++, sorear++
  • Loading branch information
moritz committed Mar 30, 2013
1 parent f348a0a commit ea0af47
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions S02-bits.pod
Expand Up @@ -500,8 +500,8 @@ It merely assigns an undefined C<Dog> prototype object to C<$spot>:
$spot.defined; # False
say $spot; # "Dog()"

Any type name used as a value is an undefined instance of that type's
prototype object, or I<type object> for short. See S12 for more on that.
Any type name used as a value is the undefined prototype object of that
type, or I<type object> for short. See S12 for more on that.

Any type name in rvalue context is parsed as a single type value and
expects no arguments following it. However, a type object responds to the
Expand Down

0 comments on commit ea0af47

Please sign in to comment.