Skip to content

Commit

Permalink
index \ in 4 different spots
Browse files Browse the repository at this point in the history
  • Loading branch information
gfldex committed Jul 24, 2016
1 parent d9a6d8e commit 066b3ba
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 0 deletions.
1 change: 1 addition & 0 deletions doc/Language/containers.pod6
Expand Up @@ -123,6 +123,7 @@ changes the contents of the other.
You've seen this situation before: it is exactly what happened with the
signature parameter marked as C<is rw>.
X<|\,container binding
Sigilless variables also bind by default and so do parameters with the trait C<is raw>.
my $a = 42;
Expand Down
1 change: 1 addition & 0 deletions doc/Language/quoting.pod6
Expand Up @@ -74,6 +74,7 @@ L<say> B<">My favorite color is B<$color>!B<">
My favorite color is blue!
X<|\,quoting>
The C<qq> form -- usually written using double quotes -- allows for
interpolation of backslash sequences and variables, i.e., variables can be
written within the string so that the content of the variable is inserted into
Expand Down
1 change: 1 addition & 0 deletions doc/Language/variables.pod6
Expand Up @@ -126,6 +126,7 @@ C<$num = 42> is not is own separate expression.
See L<operators|/language/operators> for more details on precedence.
=head2 Sigilless variables
X<|\,sigilless variables>
It is possible to create "variables" in Perl 6 that do not have sigils:
Expand Down
1 change: 1 addition & 0 deletions doc/Type/Scalar.pod6
Expand Up @@ -68,6 +68,7 @@ alter the value of both variables by altering only one of them:
$b = 2;
$a.say; # says "2"
X<|\,sigilless scalar>
SSA-style constants bind directly to their value with no
intervening C<Scalar>, even when C<=>/assignment is used. They may
be forced to use a C<Scalar> by assigning a C<$>-sigiled variable
Expand Down

0 comments on commit 066b3ba

Please sign in to comment.