diff --git a/doc/Language/5to6-nutshell.rakudoc b/doc/Language/5to6-nutshell.rakudoc index ae0045c8a..04f634cfd 100644 --- a/doc/Language/5to6-nutshell.rakudoc +++ b/doc/Language/5to6-nutshell.rakudoc @@ -1430,7 +1430,7 @@ Removed. =item C<-P> C<-u> C<-U> C<-W> C<-X> Removed. See -L. +L. =item C<-w> diff --git a/doc/Language/5to6-perlfunc.rakudoc b/doc/Language/5to6-perlfunc.rakudoc index 21e3dc313..f7a52af42 100644 --- a/doc/Language/5to6-perlfunc.rakudoc +++ b/doc/Language/5to6-perlfunc.rakudoc @@ -439,9 +439,9 @@ an entity, and C<%hash.antipairs> does the same with the keys and values reverse Incidentally, what we have there with the C«->» is called a pointy block and, though there are a number of examples in the documentation, there doesn't seem to be a really clear explanation of how they work. -L may be of some +L may be of some help here, as well as the design document at -L. There is also +L. There is also some information at L The Raku ecosystem has a module L|https://raku.land/zef:lizmat/P5each> @@ -1359,7 +1359,7 @@ C<$foo> will treat C<$foo> as a literal string, and using C«<$foo>» will interpret the contents of C<$foo> as regex code. Note that the angle brackets are doing something different here than they do outside a regex. For more information on this, see -L +L The Raku ecosystem has a module L|https://raku.land/zef:lizmat/P5quotemeta> which exports a C function that mimics the original Perl @@ -1559,7 +1559,7 @@ C can be used as a function, defaulting to standard out. To use C as a function with a filehandle I of standard out, you need to put a colon after the filehandle. I. e. C. The use of the colon as an "invocant marker" here is discussed at -L. Alternately, you can use +L. Alternately, you can use a method call: C<$fh.say("howdy!")> The Raku ecosystem has a module L|https://raku.land/zef:lizmat/P5print> diff --git a/doc/Language/5to6-perlop.rakudoc b/doc/Language/5to6-perlop.rakudoc index 7f8f9dc1d..ba058adb9 100644 --- a/doc/Language/5to6-perlop.rakudoc +++ b/doc/Language/5to6-perlop.rakudoc @@ -322,7 +322,7 @@ documented, called C<.trans>. C<.trans> uses a list of pairs, as follows: C«$x.trans(['a'..'c'] => ['A'..'C'], ['d'..'q'] => ['D'..'Q'], ['r'..'z'] => ['R'..'Z']);». A much more extensive description of the uses of C<.trans> can be found at -L. The C +L. The C equivalent has been done away with. Heredocs are specified differently in Raku. You use C<:to> with your quoting diff --git a/doc/Language/5to6-perlsyn.rakudoc b/doc/Language/5to6-perlsyn.rakudoc index 808a7b2d7..6c66bb7aa 100644 --- a/doc/Language/5to6-perlsyn.rakudoc +++ b/doc/Language/5to6-perlsyn.rakudoc @@ -170,14 +170,14 @@ for ^10 { # inner for =end code -For what is planned for C, see L. +For what is planned for C, see L. =head2 Ellipsis statement C<...> (along with C and C) are used to create stub declarations. This is a bit more complicated than the use of C<...> in Perl, so you'll probably want to look at -L for the gory +L for the gory details. That said, there doesn't seem to be an I reason why it shouldn't still fulfill the role it did in Perl, despite its role being expanded in Raku. diff --git a/doc/Language/5to6-perlvar.rakudoc b/doc/Language/5to6-perlvar.rakudoc index fd9a6a9a6..9402ca789 100644 --- a/doc/Language/5to6-perlvar.rakudoc +++ b/doc/Language/5to6-perlvar.rakudoc @@ -316,7 +316,7 @@ Does not exist in Raku, but you can get the same information using C<$/[*- If you want to I why that works, you can look at these documents: L<[ ] routine|/routine/[ ]>, L|/type/Whatever>, -and the L +and the L =head3 $LAST_SUBMATCH_RESULT, $^N diff --git a/doc/Language/glossary.rakudoc b/doc/Language/glossary.rakudoc index 86dc2e91b..5ac7de78d 100644 --- a/doc/Language/glossary.rakudoc +++ b/doc/Language/glossary.rakudoc @@ -744,7 +744,7 @@ of an operator and operands that can be subexpressions or Ls. Operators are an alternative syntax for a L. With that syntax, what would be the arguments of the function are named operands instead. Operators are classified into -L of +L of categories. A category has a precedence, an arity, and can be L, L, L. Raku is very creative as to what is an operator, so there are many categories. Operators are made of many tokens, possibly with diff --git a/doc/Language/haskell-to-p6.rakudoc b/doc/Language/haskell-to-p6.rakudoc index acfb5f0aa..3146e5c1e 100644 --- a/doc/Language/haskell-to-p6.rakudoc +++ b/doc/Language/haskell-to-p6.rakudoc @@ -439,7 +439,7 @@ And in Raku: =end code See this design document for more information on what kinds of list comprehensions are possible -in: L. +in: L. As you can see, when you get into some more advanced Haskell list comprehensions, Raku does not translate exactly the same, but it's possible to do the same things, nonetheless. diff --git a/doc/Language/list.rakudoc b/doc/Language/list.rakudoc index 4fa84d8ea..7c2c15a15 100644 --- a/doc/Language/list.rakudoc +++ b/doc/Language/list.rakudoc @@ -174,7 +174,7 @@ my @a = 1,2; .say for $[@a, |@a ]; # OUTPUT: «[[1 2] 1 2]␤» In the second case, the single argument is a single element, since we have itemized the array. There's an exception to the single argument rule -L: +L: list or arrays with a single element will be flattened: =for code diff --git a/doc/Language/modules.rakudoc b/doc/Language/modules.rakudoc index 54c1032ed..043fbe735 100644 --- a/doc/Language/modules.rakudoc +++ b/doc/Language/modules.rakudoc @@ -47,7 +47,7 @@ have the same structure as any distribution in the Perl family of languages: there is a main project directory containing a C and a C file, a C directory for the source files, which may be individually referred to as modules and/or may themselves define modules with the C keyword N says: Confusing? Yes it +L says: Confusing? Yes it is.> , a C directory for tests, and possibly a C directory for executable programs and scripts. @@ -821,7 +821,7 @@ L. In the case of the B license, which =item If you can't find your license on C or you use your own license, you should put the license's name in the license field. For more details see -L. +L. =item If you don't yet have any tests, you can leave out the C directory and C file for now. For more information on how to write @@ -894,7 +894,7 @@ possibly displayed on the module page if it's published, but you have no obligation to use it. For choosing a version numbering scheme, try and use "major.minor.patch" (see -L for +L for further details). This will go into the C key of C. This field is optional, but used by installation to match against installed version, if one exists. The C field is also mandatory, and includes a short @@ -1007,7 +1007,7 @@ you check the correctness of the META6.json file; this module will check for all the mandatory fields and that the type used for all of them is correct. There are more fields described in the -L design documents|https://design.raku.org/S22.html#META6.json>, +L design documents|https://github.com/Raku/old-design-docs/blob/master/S22-package-format.pod#META6.json>, but not all of these are implemented by existing package managers. Hence you should stick to the fields described in the above example block to ensure compatibility with existing diff --git a/doc/Language/performance.rakudoc b/doc/Language/performance.rakudoc index 9ad370362..ec7ec2ec0 100644 --- a/doc/Language/performance.rakudoc +++ b/doc/Language/performance.rakudoc @@ -176,7 +176,7 @@ more efficient for that case. =head2 Speed up type-checks and call resolution Most L clauses|/language/signatures#Type_constraints> – and thus most -L – force dynamic +L – force dynamic (runtime) type checking and call resolution for any call it I match. This is slower, or at least later, than compile-time. diff --git a/doc/Language/rb-nutshell.rakudoc b/doc/Language/rb-nutshell.rakudoc index 597d14efa..9034553dd 100644 --- a/doc/Language/rb-nutshell.rakudoc +++ b/doc/Language/rb-nutshell.rakudoc @@ -495,7 +495,7 @@ Please note that, in this case, C<===> is not symmetric; in the first and last case, the variable has to be in the right-hand side. There is no equivalent to the signature class in Ruby, either. -See L for more information on this feature. +See L for more information on this feature. =head2 C<& | ^> Numeric bitwise ops =head2 C<& | ^> Boolean ops @@ -774,7 +774,7 @@ next if $line.match(/static/); # Raku Alternately, the C<.match> and C<.subst> methods can be used. Note that C<.subst> is non-mutating. See -L. +L. =head2 C<.sub> and C<.sub!> diff --git a/doc/Language/regexes.rakudoc b/doc/Language/regexes.rakudoc index 62d990a0f..36c7bc9cd 100644 --- a/doc/Language/regexes.rakudoc +++ b/doc/Language/regexes.rakudoc @@ -1000,7 +1000,7 @@ In short, in regex branches separated by C<|>, the longest token match wins, independent of the textual ordering in the regex. However, what C<|> really does is more than that. It does not decide which branch wins after finishing the whole match, -but follows the L. +but follows the L. Briefly, what C<|> does is this: @@ -1033,7 +1033,7 @@ If the tie breaker above doesn't work, then the textually earlier alternative takes precedence. For more details, see -L. +L. =head2 Quoted lists are LTM matches diff --git a/doc/Language/syntax.rakudoc b/doc/Language/syntax.rakudoc index d1c7c95be..63a6c8862 100644 --- a/doc/Language/syntax.rakudoc +++ b/doc/Language/syntax.rakudoc @@ -569,7 +569,7 @@ See L for many more options, including L|/language/quoting#Interpolation:_qq>. Raku uses the standard escape characters in literals: C<\0 \a \b \t \n \f \r \e>, with the same meaning as the ASCII escape codes, specified in -L. +L. say "🔔\a"; # OUTPUT: «🔔␇␤»