Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Merge pull request #92 from lucasbuchala/random-changes1
Miscellaneous changes
  • Loading branch information
zoffixznet committed Apr 4, 2015
2 parents dcd6f6c + 43579ec commit c040f33
Show file tree
Hide file tree
Showing 6 changed files with 25 additions and 22 deletions.
18 changes: 9 additions & 9 deletions S02-bits.pod
Expand Up @@ -84,19 +84,19 @@ If a character is already used in Ps/Pe/Pi/Pf mappings, then any entry in
BidiMirroring is ignored (both forward and backward mappings). For any
given Ps character, the next Pe codepoint (in numerical order) is assumed to
be its matching character even if that is not what you might guess using
left-right symmetry. Therefore C<U+298D> () maps to C<U+298E> (), not C<U+2990> (),
and C<U+298F> () maps to C<U+2990> (), not C<U+298E> (). Neither C<U+298E> () nor
C<U+2990> () are valid bracket openers, despite having reverse mappings in the
left-right symmetry. Therefore C<U+298D> (C<⦍>) maps to C<U+298E> (C<⦎>), not C<U+2990> (C<⦐>),
and C<U+298F> (C<⦏>) maps to C<U+2990> (C<⦐>), not C<U+298E> (C<⦎>). Neither C<U+298E> (C<⦎>) nor
C<U+2990> (C<⦐>) are valid bracket openers, despite having reverse mappings in the
BidiMirroring table.

The C<U+301D> () codepoint has two closing alternatives, C<U+301E> () and
C<U+301F> (); Perl 6 only recognizes the one with lower code point number,
C<U+301E> (), as the closing brace. This policy also applies to new
The C<U+301D> (C<〝>) codepoint has two closing alternatives, C<U+301E> (C<〞>) and
C<U+301F> (C<〟>); Perl 6 only recognizes the one with lower code point number,
C<U+301E> (C<〞>), as the closing brace. This policy also applies to new
one-to-many mappings introduced in the future.

However, many-to-one mappings are fine; multiple opening characters may map
to the same closing character. For instance, C<U+2018> (), C<U+201A> (), and
C<U+201B> () may all be used as the opener for the C<U+2019> () closer.
to the same closing character. For instance, C<U+2018> (C<‘>), C<U+201A> (C<‚>), and
C<U+201B> (C<‛>) may all be used as the opener for the C<U+2019> (C<’>) closer.
Constructs that count openers and closers assume that only the given opener
is special. That is, if you open with one of the alternatives, all other
alternatives are treated as non-bracketing characters within that construct.
Expand Down Expand Up @@ -297,7 +297,7 @@ backslashing conventions in surrounding cultures. Hence you must write an
explicit whitespace match some other way, such as with quotes or with a
C<\x20> or C<\c32> escape. On the other hand, while an unspace can start
with C<\#> in normal code, C<\#> within a regex is specifically allowed, and
is not taken as unspace, but matches a literal U+0023, NUMBER SIGN. (Within
is not taken as unspace, but matches a literal C<U+0023> (NUMBER SIGN). (Within
a character class, you may also escape whitespace with a backslash; the
restriction on unspace applies only at the normal pattern-matching level.)

Expand Down
10 changes: 5 additions & 5 deletions S03-operators.pod
Expand Up @@ -1110,7 +1110,7 @@ C<< infix:<~> >>, string/buffer concatenation

=item *

C<< infix:<&> >>, all() operator
C<< infix:<&> >>, C<all()> operator

$a & $b & $c ...

Expand All @@ -1136,7 +1136,7 @@ tests don't pass. This cannot be guaranteed by:

=item *

C<< infix:<|> >>, any() operator
C<< infix:<|> >>, C<any()> operator

$a | $b | $c ...

Expand All @@ -1159,7 +1159,7 @@ of safety:

=item *

C<< infix:<^> >>, one() operator
C<< infix:<^> >>, C<one()> operator

$a ^ $b ^ $c ...

Expand Down Expand Up @@ -4196,7 +4196,7 @@ mad in the first place, which seems almost a certainty by this point.

=head2 Hyper operators

The Unicode characters C<»> (C<\x[BB]>) and C<«> (C<\x[AB]>) and
The Unicode characters C<»> (C<U+00BB>) and C<«> (C<U+00AB>) and
their ASCII digraphs C<<< >> >>> and C<<< << >>> are used to denote a
"list operation" that operates on each element of its list (or array)
argument (or arguments) and returns a single list (or array) of
Expand Down Expand Up @@ -5088,7 +5088,7 @@ the infix operator will be the variable's prototype object:

my Dog $fido .= new; # okay: a Dog object
my Dog $fido = Dog.new; # same thing
my Dog $fido = $fido.new; # wrong: invalid self-reference
my Dog $fido = $fido.new; # okay: valid self-reference
my (Dog $fido .= new); # wrong: cannot use .= inside signature

Note that very few mutating operators make sense on a type object, however,
Expand Down
2 changes: 1 addition & 1 deletion S05-regex.pod
Expand Up @@ -2221,7 +2221,7 @@ defined as any of:
U+2028 LINE SEPARATOR
U+2029 PARAGRAPH SEPARATOR

Note that U+000D CARRIAGE RETURN (CR) is considered vertical whitespace despite
Note that C<U+000D> (CARRIAGE RETURN) is considered vertical whitespace despite
the fact that it only moves the "carriage" horizontally.

=item *
Expand Down
13 changes: 8 additions & 5 deletions S19-commandline.pod
Expand Up @@ -565,17 +565,17 @@ list of arguments provided on the command-line.

=item L<http://perldoc.perl.org/perlrun.html>

=item L<http://search.cpan.org/~jv/Getopt-Long-2.37/lib/Getopt/Long.pm>
=item L<http://search.cpan.org/dist/Getopt-Long/lib/Getopt/Long.pm>

=item L<http://search.cpan.org/~dconway/Getopt-Euclid-v0.2.0/lib/Getopt/Euclid.pm>
=item L<http://search.cpan.org/dist/Getopt-Euclid/lib/Getopt/Euclid.pm>

=item L<http://design.perl6.org/S06.html#Declaring_a_MAIN_subroutine>

=item L<http://search.cpan.org/src/AUDREYT/Perl6-Pugs-6.2.13/docs/Pugs/Doc/Run.pod>
=item L<http://search.cpan.org/dist/Perl6-Pugs/docs/Pugs/Doc/Run.pod>

=item L<http://haskell.org/ghc/docs/latest/html/users_guide/using-ghc.html>

=item L<http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/java.html>
=item L<http://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html>

=back

Expand All @@ -588,14 +588,17 @@ I don't have a solution, but perhaps pass a closure that evaluates to an Int?
This should try to use whatever option does the same thing to a new
filehandle when S16 is further developed.

=for consideration
=begin consideration

[probably a setter method on $*IN of some sort? --law]

Sandboxing? maybe -r

Env var? maybe -E.
Could be posed in terms of substituting a different setting.

=end consideration

=head1 AUTHORS

Jerry Gay <jerry.gay@rakudoconsulting.com>
Expand Down
2 changes: 1 addition & 1 deletion S28-special-names.pod
Expand Up @@ -2,7 +2,7 @@

=head1 TITLE

[DRAFT] Synopsis 28 - Special Names [DRAFT]
[DRAFT] Synopsis 28 - Special Names [DRAFT]

=head1 VERSION

Expand Down
2 changes: 1 addition & 1 deletion S29-functions.pod
Expand Up @@ -4,7 +4,7 @@

Synopsis 29: Builtin Functions

=head1 Version
=head1 VERSION

Created: 12 Mar 2005

Expand Down

0 comments on commit c040f33

Please sign in to comment.