From b907392cb64c2f73dd848c67a03a72f743dc30e4 Mon Sep 17 00:00:00 2001 From: JJ Merelo Date: Tue, 29 May 2018 12:44:42 +0200 Subject: [PATCH] Chages structure of new page and adds link to structures --- doc/Language/iterating.pod6 | 1 + doc/Language/structures.pod6 | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/Language/iterating.pod6 b/doc/Language/iterating.pod6 index 2ced7e011..48cc2f7cd 100644 --- a/doc/Language/iterating.pod6 +++ b/doc/Language/iterating.pod6 @@ -12,6 +12,7 @@ TBD TBD +=head1 C loops and why we do not like them =end pod diff --git a/doc/Language/structures.pod6 b/doc/Language/structures.pod6 index 324102909..81e99e125 100644 --- a/doc/Language/structures.pod6 +++ b/doc/Language/structures.pod6 @@ -147,7 +147,7 @@ retrieve them $logger( "Stuff" ); $logger( "More stuff"); say $logger( Nil, "2018-05-28"); # OUTPUT: «(Stuff More stuff)» -» + A C has a L, in this case two arguments, the first of which is the event that is going ot be logged, and the second is the key @@ -284,7 +284,6 @@ whatever object this particular role is mixed in; in this case it will contain the hash it is mixed in with; it will contain something else (and possibly work some other way) in other case. This role will provide the C method to any variable it's mixed with, providing new, -attachable, functionalities to I variables. L can also be used to constrain the possible values a variable might hold; they are Perl 6 attempt at