Skip to content

Commit

Permalink
Merge pull request #123 from tbrowder/texas
Browse files Browse the repository at this point in the history
changes for Texas => ASCII
  • Loading branch information
zoffixznet committed Oct 14, 2017
2 parents aec7812 + 1c979ab commit f52230c
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
6 changes: 3 additions & 3 deletions S02-bits.pod
Expand Up @@ -927,7 +927,7 @@ as the fundamental unit rather than codepoints, this has some implications
regarding efficient implementation. It is suggested that all graphemes be
translated on input to unique grapheme numbers and represented as integers
within some kind of uniform array for fast substr access. For those
graphemes that have a precomposed form, use of that codepoint is suggested.
graphemes that have a precomposed form, use of that codepoint is suggested.
(Note that this means Latin-1 can still be represented internally with 8-bit
integers.)

Expand Down Expand Up @@ -2195,7 +2195,7 @@ list, so does not flatten in flat context.

When an argument is bound to a parameter, the behavior depends on whether
the parameter is "flattening" or "argumentative". Positional parameters and
slice parameters are argumentative
slice parameters are argumentative
and just return the next syntactic argument
without flattening. (A slice differs from an ordinary positional
parameter in being "slurpy", that is, it is intended to fetch multiple
Expand Down Expand Up @@ -3580,7 +3580,7 @@ you can suppress the error by putting a space inside: C<< < > >>.

Much like the relationship between single quotes and double quotes, single
angles do not interpolate while double angles do. The double angles may be
written either with French quotes, C<«$foo @bar[]»>, or with "Texas" quotes,
written either with French quotes, C<«$foo @bar[]»>, or with ASCII quotes,
C<<< <<$foo @bar[]>> >>>, as the ASCII workaround. The implicit split is
done after interpolation, but respects quotes in a shell-like fashion, so
that C<«'$foo' "@bar[]"»> is guaranteed to produce a list of two "words"
Expand Down
10 changes: 5 additions & 5 deletions S99-glossary.pod
Expand Up @@ -2538,13 +2538,13 @@ L<tail call> optimization.

The Perl 6 test suite is L</roast>

=head2 Texas operator
=head2 ASCII operator

The ASCII variant of a non-ASCII Unicode operator or symbol. So described
because "Everything's bigger in Texas." For instance, C<<< >>+<< >>> is the
"Texas" form of the C<»+«> hyper-addition operator, and C<(elem)>
The ASCII variant of a non-ASCII Unicode operator or symbol.
For instance, C<<< >>+<< >>> is the
"ASCII" form of the C<»+«> hyper-addition operator, and C<(elem)>
corresponds to the C<∈> ("Is this an element of that set?") operator that
comes from set theory. Texas operators are a workaround to the problem that
comes from set theory. ASCII operators are a workaround to the problem that
people don't know how to type Unicode yet. Culturally, while we encourage
people to use the Unicode symbols in a vague sort of way, we do not
disparage the use of the ASCII variants. Well, maybe just a little...
Expand Down

0 comments on commit f52230c

Please sign in to comment.