Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Clarify language and narrow an unitentionally wide C<>
  • Loading branch information
skids committed Jan 2, 2016
1 parent 8247afb commit e36415e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/Type/Scalar.pod
Expand Up @@ -15,7 +15,7 @@ certain places where it is important to note the presence of C<Scalar>s.
When a value is assigned to a C<$>-sigiled variable, the variable will
actually bind to a C<Scalar>, which in turn will bind to the value.
When a C<Scalar> is assigned to a C<$-sigiled> variable, the value
When a C<Scalar> is assigned to a C<$>-sigiled variable, the value
bound to by that C<Scalar> will be bound to the C<Scalar> which that
variable was bound to (a new one will be created if necessary.)
Expand Down Expand Up @@ -52,7 +52,7 @@ Array elements may be bound directly to values using C<:=> as well,
however this is to be discouraged as it may lead to confusion.
Doing so will break exact round-tripping of C<.perl> output -- since
C<Array>s are assumed to place C<Scalar>s around each element,
C<Scalar>s are not denoted with C<$> in the output of C<.perl> methods.
C<Scalar>s are not denoted with C<$> in the output of C<Array.perl>.
[1,$(2,3)].perl.say # says [1, (2, 3)]
(1,$(2,3)).perl.say # says (1, $(2, 3))
Expand Down

0 comments on commit e36415e

Please sign in to comment.