Changes between Version 5 and Version 6 of CleanupMakeHtml

Timestamp:

07/19/10 17:05:16 (12 years ago)

Author:

coke

Comment:

track latest changes WRT title.

CleanupMakeHtml

@@ -5 +5 @@
 Some likely candidates:
 
- * title isn't being pulled from document.
  * copyright year is changed.
  * some items are not being turned into {{{<a>}}} tags.
 
 make html calls tools/docs/make_html_docs.pl, which uses lib/Parrot/Docs/PodToHtml.pm - the old file is Pod2HTML, steal where appropriate.
+
+Diffs that show up but are OK.
+
+ * Title changes where extra words are properly showing up (like MSVC debugging entry)
 
 {{{
@@ -19 +22 @@
 Only in parrot-trunk/docs/html: developer.html
 Only in parrot-trunk/docs/html/docs/book/pct: ch01_introduction.pod.html
-diff -r parrot/docs/html/docs/book/pct/ch02_getting_started.pod.html parrot-trunk/docs/html/docs/book/pct/ch02_getting_started.pod.html
+diff -r parrot-trunk/docs/html/docs/book/pct/ch02_getting_started.pod.html parrot/docs/html/docs/book/pct/ch02_getting_started.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Getting Started
+---
+>                     Getting Started
+154c154
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pct/ch03_compiler_tools.pod.html parrot/docs/html/docs/book/pct/ch03_compiler_tools.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Parrot Compiler Tools
+---
+>                     Parrot Compiler Tools
+342c342
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pct/ch04_pge.pod.html parrot/docs/html/docs/book/pct/ch04_pge.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Grammar Engine
+---
+>                     Grammar Engine
+631c631
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pct/ch05_nqp.pod.html parrot/docs/html/docs/book/pct/ch05_nqp.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Grammar Actions
+---
+>                     Grammar Actions
+226c226
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch01_introduction.pod.html parrot/docs/html/docs/book/pir/ch01_introduction.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Introduction
+---
+>                     Introduction
+162c162
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch02_getting_started.pod.html parrot/docs/html/docs/book/pir/ch02_getting_started.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Getting Started
+---
+>                     Getting Started
+60c60
+< <p>To install Parrot in a different location, use the <code>&#45;&#45;prefix</code> option to <em><a href="../../../Configure.pl.html">Configure.pl</a></em>:</p>
+---
+> <p>To install Parrot in a different location, use the <code>&#45;&#45;prefix</code> option to <em>Configure.pl</em>:</p>
+87c87
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch03_basic_syntax.pod.html parrot/docs/html/docs/book/pir/ch03_basic_syntax.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Basic Syntax
+---
+>                     Basic Syntax
+216c216
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch04_variables.pod.html parrot/docs/html/docs/book/pir/ch04_variables.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Variables
+---
+>                     Variables
+279,291c279,284
+< </pre>
+< <p>Both <code>and</code> and <code>or</code> are short&#45;circuiting ops.
+< If they can determine what value to return from the first argument,
+< they&#39;ll never evaluate the second.
+< This is significant only for PMCs,
+< as they might have side effects on evaluation.</p>
+< 
+< <p>The <code>xor</code><!--
+<       INDEX: xor opcode
+< --> opcode returns the first argument if it is the only true value,
+< returns the second argument if it is the only true value,
+< and returns false if both values are true or both are false:</p>
+< <pre>  $I0 = xor 1, 0  # returns 1
+---
+> Both C<and> and C<or> are short-circuiting ops. If they can determine what
+> value to return from the first argument, they'll never evaluate the second.
+> This is significant only for PMCs, as they might have side effects on
+> evaluation.The C<xor>X<xor opcode> opcode returns the first argument if it is the only
+> true value, returns the second argument if it is the only true value, and
+> returns false if both values are true or both are false:<pre>  $I0 = xor 1, 0  # returns 1
+296,298c289,290
+< <p>The <code>not</code><!--
+<       INDEX: not opcode
+< --> opcode returns a true value when the argument is false and a false value if the argument is true:</p>
+---
+> The C<not>X<not opcode> opcode returns a true value when the argument is false
+> and a false value if the argument is true:
+302,316c294,298
+< <p><!--
+<       INDEX: bitwise opcodes
+< --> The bitwise opcodes operate on their values a single bit at a time.
+< <code>band</code><!--
+<       INDEX: band opcode
+< -->,
+< <code>bor</code><!--
+<       INDEX: bor opcode
+< -->,
+< and <code>bxor</code><!--
+<       INDEX: bxor opcode
+< --> return a value that is the logical AND,
+< OR,
+< or XOR of each bit in the source arguments.
+< They each take two arguments.</p>
+---
+> X<bitwise opcodes>
+> The bitwise opcodes operate on their values a single bit at a time.
+> C<band>X<band opcode>, C<bor>X<bor opcode>, and C<bxor>X<bxor opcode> return a
+> value that is the logical AND, OR, or XOR of each bit in the source arguments.
+> They each take two arguments.
+324,326c306,307
+< <p><code>band</code>,
+< <code>bor</code>,
+< and <code>bxor</code> also have variants that modify the result in place.</p>
+---
+> C<band>, C<bor>, and C<bxor> also have variants that modify the result
+> in place.
+334,336c315
+< <p><code>bnot</code><!--
+<       INDEX: bnot opcode
+< --> is the logical NOT of each bit in the source argument.</p>
+---
+> C<bnot>X<bnot opcode> is the logical NOT of each bit in the source argument.
+343,349c322,326
+< <p><!--
+<       INDEX: shl opcode
+< --> <!--
+<       INDEX: shr opcode
+< --> <!--
+<       INDEX: lsr opcode
+< --> The logical and arithmetic shift operations shift their values by a specified number of bits:</p>
+---
+> X<shl opcode>
+> X<shr opcode>
+> X<lsr opcode>
+> The logical and arithmetic shift operations shift their values by a specified
+> number of bits:
+361,372c338,344
+< <p><!--
+<       INDEX: strings
+< --> Parrot strings are buffers of variable&#45;sized data.
+< The most common use of strings is to store text data.
+< Strings can also hold binary or other non&#45;textual data,
+< though this is rare.In general,
+< a custom PMC is more useful. Parrot strings are flexible and powerful,
+< to handle the complexity of human&#45;readable (and computer&#45;representable) text data.
+< String operations work with string literals,
+< variables,
+< and constants,
+< and with string&#45;like PMCs.</p>
+---
+> X<strings>
+> Parrot strings are buffers of variable-sized data. The most common use of
+> strings is to store text data. Strings can also hold binary or other
+> non-textual data, though this is rare.N<In general, a custom PMC is more
+> useful.> Parrot strings are flexible and powerful, to handle the complexity of
+> human-readable (and computer-representable) text data.  String operations work
+> with string literals, variables, and constants, and with string-like PMCs.
+377,381c349,353
+< <p><!--
+<       INDEX: string escapes
+< --> <!--
+<       INDEX: escape sequences
+< --></p>
+---
+> X<string escapes>
+> X<escape sequences>
+> 
+> Strings in double-quotes allow escape sequences using backslashes. Strings in
+> single-quotes only allow escapes for nested quotes:
+383,384c355,356
+< <p>Strings in double&#45;quotes allow escape sequences using backslashes.
+< Strings in single&#45;quotes only allow escapes for nested quotes:</p>
+---
+>   $S0 = "This string is \n on two lines"
+>   $S0 = 'This is a \n one-line string with a slash in it'
+386,387d357
+< <pre>  $S0 = &#34;This string is \n on two lines&#34;
+<   $S0 = &#39;This is a \n one&#45;line string with a slash in it&#39;</pre>
+389c359,360
+< <p>Table 4.1 shows the escape sequences Parrot supports in double&#45;quoted strings.</p>
+---
+> Table 4.1 shows the escape sequences Parrot supports in double-quoted
+> strings.
+394,396c365,375
+< <p><!--
+<       INDEX: heredocs
+< --> If you need more flexibility in defining a string, use a heredoc string literal. The <code>&#60;&#60;</code> operator starts a heredoc. The string terminator immediately follows. All text until the terminator is part of the string. The terminator must appear on its own line, must appear at the beginning of the line, and may not have any trailing whitespace.</p>
+---
+> X<heredocs>
+> If you need more flexibility in defining a string, use a heredoc string
+> literal. The C<E<lt>E<lt>> operator starts a heredoc.  The string terminator
+> immediately follows. All text until the terminator is part of the string. The
+> terminator must appear on its own line, must appear at the beginning of the
+> line, and may not have any trailing whitespace.
+> 
+>   $S2 = <<"End_Token"
+>   This is a multi-line string literal. Notice that
+>   it doesn't use quotation marks.
+>   End_Token
+398,401d376
+< <pre>  $S2 = &#60;&#60;&#34;End_Token&#34;
+<   This is a multi&#45;line string literal. Notice that
+<   it doesn&#39;t use quotation marks.
+<   End_Token</pre>
+406,410c381,382
+< <p><!--
+<       INDEX: . operator
+< --> <!--
+<       INDEX: strings;concatenation
+< --></p>
+---
+> X<. operator>
+> X<strings;concatenation>
+412c384,386
+< <p>Use the <code>.</code> operator to concatenate strings. The following example concatenates the string &#34;cd&#34; onto the string &#34;ab&#34; and stores the result in <code>$S1</code>.</p>
+---
+> Use the C<.> operator to concatenate strings. The following example
+> concatenates the string "cd" onto the string "ab" and stores the result in
+> C<$S1>.
+417,419c391,394
+< <p><!--
+<       INDEX: .= operator
+< --> Concatenation has a <code>.=</code> variant to modify the result in place. In the next example, the <code>.=</code> operation appends &#34;xy&#34; onto the string &#34;abcd&#34; in <code>$S1</code>.</p>
+---
+> X<.= operator>
+> Concatenation has a C<.=> variant to modify the result in place. In the
+> next example, the C<.=> operation appends "xy" onto the string "abcd" in
+> C<$S1>.
+426,428c401,402
+< <p><!--
+<       INDEX: repeat opcode
+< --> The <code>repeat</code> opcode repeats a string a specified number of times:</p>
+---
+> X<repeat opcode>
+> The C<repeat> opcode repeats a string a specified number of times:
+433c407,408
+< <p>In this example, <code>repeat</code> generates a new string with &#34;a&#34; repeated five times and stores it in <code>$S1</code>.</p>
+---
+> In this example, C<repeat> generates a new string with "a" repeated five
+> times and stores it in C<$S1>.
+438,440c413,415
+< <p><!--
+<       INDEX: length opcode
+< --> The <code>length</code> opcode returns the length of a string in characters. This won&#39;t be the same as the length in <i>bytes</i> for multibyte encoded strings:</p>
+---
+> X<length opcode>
+> The C<length> opcode returns the length of a string in characters. This won't
+> be the same as the length in I<bytes> for multibyte encoded strings:
+445c420
+< <p><code>length</code> has no equivalent for PMC strings.</p>
+---
+> C<length> has no equivalent for PMC strings.
+450,452c425,428
+< <p>The simplest version of the <code>substr</code><!--
+<       INDEX: substr opcode
+< --> opcode takes three arguments: a source string, an offset position, and a length. It returns a substring of the original string, starting from the offset position (0 is the first character) and spanning the length:</p>
+---
+> The simplest version of the C<substr>X<substr opcode> opcode takes three
+> arguments: a source string, an offset position, and a length. It returns a
+> substring of the original string, starting from the offset position (0 is the
+> first character) and spanning the length:
+455,457c431,444
+< <p>This example extracts a two&#45;character string from &#34;abcde&#34; at a one&#45;character offset from the beginning of the string (starting with the second character). It generates a new string, &#34;bc&#34;, in the destination register <code>$S0</code>.</p>
+< 
+< <p>When the offset position is negative, it counts backward from the end of the string. Thus an offset of &#45;1 starts at the last character of the string.</p>
+---
+> This example extracts a two-character string from "abcde" at a one-character
+> offset from the beginning of the string (starting with the second character).
+> It generates a new string, "bc", in the destination register C<$S0>.
+> 
+> When the offset position is negative, it counts backward from the end of the
+> string. Thus an offset of -1 starts at the last character of the string.
+> 
+> C<substr> no longer has a four-argument form, as in-place string operations
+> have been removed.  There is a C<replace> operator which will perform the
+> replacement and return a new_string without modifying the old_string.
+> The arguments are new_string, old_string, offset, count and
+> replacement_string.  The old_string is copied to the new_string with the
+> replacement_string inserted from offset replacing the content for count
+> characters.
+459,461c446,447
+< <p><code>substr</code> no longer has a four&#45;argument form, as in&#45;place string operations have been removed. There is a <code>replace</code> operator which will perform the replacement and return a new_string without modifying the old_string. The arguments are new_string, old_string, offset, count and replacement_string. The old_string is copied to the new_string with the replacement_string inserted from offset replacing the content for count characters.</p>
+< 
+< <p>This example replaces the substring &#34;bc&#34; in <code>$S1</code> with the string &#34;XYZ&#34;, and returns &#34;aXYZde&#34; in <code>$S0</code>, <code>$S1</code> is not changed:</p>
+---
+> This example replaces the substring "bc" in C<$S1> with the string "XYZ",
+> and returns "aXYZde" in C<$S0>, C<$S1> is not changed:
+467c453,456
+< <p>When the offset position in a <code>replace</code> is one character beyond the original string length, <code>replace</code> appends the replacement string just like the concatenation operator. If the replacement string is an empty string, the opcode removes the characters from the original string in the new string.</p>
+---
+> When the offset position in a C<replace> is one character beyond the original
+> string length, C<replace> appends the replacement string just like the
+> concatenation operator. If the replacement string is an empty string, the
+> opcode removes the characters from the original string in the new string.
+475,479c464,469
+< <p>The <code>chr</code><!--
+<       INDEX: chr opcode
+< --> opcode takes an integer value and returns the corresponding character in the ASCII character set as a one&#45;character string. The <code>ord</code><!--
+<       INDEX: ord opcode
+< --> opcode takes a single character string and returns the integer value of the character at the first position in the string. The integer value of the character will differ depending on the current encoding of the string:</p>
+---
+> The C<chr>X<chr opcode> opcode takes an integer value and returns the
+> corresponding character in the ASCII character set as a one-character string.
+> The C<ord>X<ord opcode> opcode takes a single character string and returns the
+> integer value of the character at the first position in the string. The integer
+> value of the character will differ depending on the current encoding of the
+> string:
+483c473,475
+< <p><code>ord</code> has a two&#45;argument variant that takes a character offset to select a single character from a multicharacter string. The offset must be within the length of the string:</p>
+---
+> C<ord> has a two-argument variant that takes a character offset to select
+> a single character from a multicharacter string. The offset must be within
+> the length of the string:
+486c478,479
+< <p>A negative offset counts backward from the end of the string, so &#45;1 is the last character.</p>
+---
+> A negative offset counts backward from the end of the string, so -1 is
+> the last character.
+492,494c485
+< <p><!--
+<       INDEX: strings;formatting
+< --></p>
+---
+> X<strings;formatting>
+496,498c487,490
+< <p>The <code>sprintf</code><!--
+<       INDEX: sprintf opcode
+< --> opcode generates a formatted string from a series of values. It takes two arguments: a string specifying the format, and an array PMC containing the values to be formatted. The format string and the result can be either strings or PMCs:</p>
+---
+> The C<sprintf>X<sprintf opcode> opcode generates a formatted string from a
+> series of values. It takes two arguments: a string specifying the format, and
+> an array PMC containing the values to be formatted. The format string and the
+> result can be either strings or PMCs:
+502,508c494,510
+< <p>The format string is similar to C&#39;s <code>sprintf</code> function with extensions for Parrot data types. Each format field in the string starts with a <code>%</code> and ends with a character specifying the output format. Table 4.2 lists the available output format characters.</p>
+< 
+< <p>Each format field supports several specifier options: flags, width, precision, and size. Table 4.3 lists the format flags.</p>
+< 
+< <p>The width is a number defining the minimum width of the output from a field. The precision is the maximum width for strings or integers, and the number of decimal places for floating&#45;point fields. If either width or precision is an asterisk (<code>*</code>), it takes its value from the next argument in the PMC.</p>
+< 
+< <p>The size modifier defines the type of the argument the field takes. Table 4.4 lists the size flags. The values in the aggregate PMC must have a type compatible with the specified size.</p>
+---
+> The format string is similar to C's C<sprintf> function with extensions for
+> Parrot data types. Each format field in the string starts with a C<%> and ends
+> with a character specifying the output format. Table 4.2 lists the available
+> output format characters.
+> 
+> Each format field supports several specifier options: R<flags>, R<width>,
+> R<precision>, and R<size>.  Table 4.3 lists the format flags.
+> 
+> The R<width> is a number defining the minimum width of the output from
+> a field. The R<precision> is the maximum width for strings or
+> integers, and the number of decimal places for floating-point fields.
+> If either R<width> or R<precision> is an asterisk (C<*>), it takes its
+> value from the next argument in the PMC.
+> 
+> The R<size> modifier defines the type of the argument the field takes.
+> Table 4.4 lists the size flags. The values in the aggregate PMC must
+> have a type compatible with the specified R<size>.
+512c514,519
+< <p>The format string of this <code>sprintf</code> example has two format fields. The first, <code>%#Px</code>, extracts a PMC argument (<code>P</code>) from the aggregate <code>$P2</code> and formats it as a hexadecimal integer (<code>x</code>) with a leading 0x (<code>#</code>). The second format field, <code>%+2.3Pf</code>, takes a PMC argument (<code>P</code>) and formats it as a floating&#45;point number (<code>f</code>) with a minimum of two whole digits and a maximum of three decimal places (<code>2.3</code>) and a leading sign (<code>+</code>).</p>
+---
+> The format string of this C<sprintf> example has two format fields. The first,
+> C<%#Px>, extracts a PMC argument (C<P>) from the aggregate C<$P2> and formats
+> it as a hexadecimal integer (C<x>) with a leading 0x (C<#>). The second format
+> field, C<%+2.3Pf>, takes a PMC argument (C<P>) and formats it as a
+> floating-point number (C<f>) with a minimum of two whole digits and a maximum
+> of three decimal places (C<2.3>) and a leading sign (C<+>).
+514c521,522
+< <p>The test files <em><a href="../../../t/op/string.t.html">t/op/string.t</a></em> and <em><a href="../../../t/op/sprintf.t.html">t/op/sprintf.t</a></em> have many more examples of format strings.</p>
+---
+> The test files F<t/op/string.t> and F<t/op/sprintf.t> have many more
+> examples of format strings.
+519,521c527,529
+< <p>The <code>join</code><!--
+<       INDEX: join opcode
+< --> opcode joins the elements of an array PMC into a single string. The first argument separates the individual elements of the PMC in the final string result.</p>
+---
+> The C<join>X<join opcode> opcode joins the elements of an array PMC into
+> a single string. The first argument separates the individual elements of
+> the PMC in the final string result.
+531c539,541
+< <p>This example builds a <code>Array</code> in <code>$P0</code> with the values <code>&#34;hi&#34;</code>, <code>0</code>, <code>1</code>, <code>0</code>, and <code>&#34;parrot&#34;</code>. It then joins those values (separated by the string <code>&#34;__&#34;</code>) into a single string stored in <code>$S0</code>.</p>
+---
+> This example builds a C<Array> in C<$P0> with the values C<"hi">, C<0>, C<1>,
+> C<0>, and C<"parrot">. It then joins those values (separated by the string
+> C<"__">) into a single string stored in C<$S0>.
+536c546,547
+< <p>Splitting a string yields a new array containing the resulting substrings of the original string.</p>
+---
+> Splitting a string yields a new array containing the resulting substrings of
+> the original string.
+538c549,551
+< <p>This example splits the string &#34;abc&#34; into individual characters and stores them in an array in <code>$P0</code>. It then prints out the first and third elements of the array.</p>
+---
+> This example splits the string "abc" into individual characters and stores them
+> in an array in C<$P0>. It then prints out the first and third elements of the
+> array.
+548,550c561,564
+< <p>The <code>index</code><!--
+<       INDEX: index opcode
+< --> opcode searches for a substring within a string. If it finds the substring, it returns the position where the substring was found as a character offset from the beginning of the string. If it fails to find the substring, it returns &#45;1:</p>
+---
+> The C<index>X<index opcode> opcode searches for a substring
+> within a string. If it finds the substring, it returns the position
+> where the substring was found as a character offset from the beginning
+> of the string. If it fails to find the substring, it returns -1:
+556c570,571
+< <p><code>index</code> also has a three&#45;argument version, where the final argument defines an offset position for starting the search.</p>
+---
+> C<index> also has a three-argument version, where the final argument
+> defines an offset position for starting the search.
+560c575,576
+< <p>This example finds the second &#34;eb&#34; in &#34;Beeblebrox&#34; instead of the first, because the search skips the first three characters in the string.</p>
+---
+> This example finds the second "eb" in "Beeblebrox" instead of the first,
+> because the search skips the first three characters in the string.
+565,571c581,585
+< <p>The numeric bitwise opcodes also have string variants for AND, OR, and XOR: <code>bors</code><!--
+<       INDEX: bors opcode
+< -->, <code>bands</code><!--
+<       INDEX: bands opcode
+< -->, and <code>bxors</code><!--
+<       INDEX: bxors opcode
+< -->. These take string or string&#45;like PMC arguments and perform the logical operation on each byte of the strings to produce the result string. Remember that in&#45;place string operations are no longer available.</p>
+---
+> The numeric bitwise opcodes also have string variants for AND, OR, and XOR:
+> C<bors>X<bors opcode>, C<bands>X<bands opcode>, and C<bxors>X<bxors opcode>.
+> These take string or string-like PMC arguments and perform the logical
+> operation on each byte of the strings to produce the result string.
+> Remember that in-place string operations are no longer available.
+581c595,596
+< <p>The bitwise string opcodes produce meaningful results only when used with simple ASCII strings, because Parrot performs bitwise operations per byte.</p>
+---
+> The bitwise string opcodes produce meaningful results only when used with
+> simple ASCII strings, because Parrot performs bitwise operations per byte.
+586,590c601,604
+< <p>Strings use copy&#45;on&#45;write (COW)<!--
+<       INDEX: copy&#45;on&#45;write
+< --><!--
+<       INDEX: COW (copy&#45;on&#45;write)
+< --> optimizations. A call to <code>$S1 = $S0</code> doesn&#39;t immediately make a copy of <code>$S0</code>, it only makes both variables point to the same string. Parrot doesn&#39;t make a copy of the string until one of two strings is modified.</p>
+---
+> Strings use copy-on-write (COW)X<copy-on-write>X<COW (copy-on-write)>
+> optimizations. A call to C<$S1 = $S0> doesn't immediately make a copy of
+> C<$S0>, it only makes both variables point to the same string. Parrot
+> doesn't make a copy of the string until one of two strings is modified.
+597c611,614
+< <p>Modifying one of the two variables causes Parrot to create a new string. This example preserves the existing value in <code>$S0</code> and assigns the new value to the new string in <code>$S1</code>. The benefit of copy&#45;on&#45;write is avoiding the cost of copying strings until the copies are necessary.</p>
+---
+> Modifying one of the two variables causes Parrot to create a new string.  This
+> example preserves the existing value in C<$S0> and assigns the new value to the
+> new string in C<$S1>. The benefit of copy-on-write is avoiding the cost of
+> copying strings until the copies are necessary.
+602,610c619,637
+< <p><!--
+<       INDEX: charset
+< --> <!--
+<       INDEX: ASCII character set
+< --> <!--
+<       INDEX: encoding
+< --> Years ago, strings only needed to support the ASCII character set (or charset), a mapping of 128 bit patterns to symbols and English&#45;language characters. This worked as long as everyone using a computer read and wrote English and only used a small handful of punctuation symbols. In other words, it was woefully insufficient. A modern string system must manage charsets in order to make sense out of all the string data in the world. A modern string system must also handle different encodings &#45;&#45; ways to represent various charsets in memory and on disk.</p>
+< 
+< <p>Every string in Parrot has an associated encoding and character set. The default charset is 8&#45;bit ASCII, which is almost universally supported. Double&#45;quoted string constants can have an optional prefix specifying the string&#39;s encoding and charset.As you might suspect, single&#45;quoted strings do not support this. Parrot tracks information about encoding and charset internally, and automatically converts strings when necessary to preserve these characteristics. Strings constants may have prefixes of the form <code>encoding:charset:</code>.</p>
+---
+> X<charset>
+> X<ASCII character set>
+> X<encoding>
+> Years ago, strings only needed to support the ASCII character set (or
+> charset), a mapping of 128 bit patterns to symbols and English-language
+> characters. This worked as long as everyone using a computer read and
+> wrote English and only used a small handful of punctuation symbols. In
+> other words, it was woefully insufficient. A modern string system must
+> manage charsets in order to make sense out of all the string data in the
+> world. A modern string system must also handle different encodings --
+> ways to represent various charsets in memory and on disk.
+> 
+> Every string in Parrot has an associated encoding and character set. The default
+> charset is 8-bit ASCII, which is almost universally supported.  Double-quoted
+> string constants can have an optional prefix specifying the string's encoding
+> and charset.N<As you might suspect, single-quoted strings do not support this.>
+> Parrot tracks information about encoding and charset internally, and
+> automatically converts strings when necessary to preserve these
+> characteristics. Strings constants may have prefixes of the form C<encoding:charset:>.
+616,630c643,663
+< <p><!--
+<       INDEX: ISO 8859&#45;1 character set
+< --> <!--
+<       INDEX: Latin 1 character set
+< --> <!--
+<       INDEX: UCS&#45;2 encoding
+< --> <!--
+<       INDEX: UTF&#45;8 encoding
+< --> <!--
+<       INDEX: UTF&#45;16 encoding
+< --> Parrot supports the character sets <code>ascii</code>, <code>binary</code>, <code>iso&#45;8859&#45;1</code> (Latin 1), and <code>unicode</code> and the encodings <code>fixed_8</code>, <code>ucs2</code>, <code>utf8</code>, and <code>utf16</code>.</p>
+< 
+< <p>The <code>binary</code> charset treats the string as a buffer of raw unformatted binary data. It isn&#39;t really a string per se, because binary data contains no readable characters. This exists to support libraries which manipulate binary data that doesn&#39;t easily fit into any other primitive data type.</p>
+< 
+< <p>When Parrot operates on two strings (as in concatenation or comparison), they must both use the same character set and encoding. Parrot will automatically upgrade one or both of the strings to the next highest compatible format as necessary. ASCII strings will automatically upgrade to UTF&#45;8 strings if needed, and UTF&#45;8 will upgrade to UTF&#45;16. All of these conversions happen inside Parrot, so the programmer doesn&#39;t need to worry about the details.</p>
+---
+> X<ISO 8859-1 character set>
+> X<Latin 1 character set>
+> X<UCS-2 encoding>
+> X<UTF-8 encoding>
+> X<UTF-16 encoding>
+> Parrot supports the character sets C<ascii>, C<binary>, C<iso-8859-1>
+> (Latin 1), and C<unicode> and the encodings C<fixed_8>, C<ucs2>,
+> C<utf8>, and C<utf16>.
+> 
+> The C<binary> charset treats the string as a buffer of raw unformatted
+> binary data. It isn't really a string per se, because binary data
+> contains no readable characters. This exists to support libraries which
+> manipulate binary data that doesn't easily fit into any other primitive
+> data type.
+> 
+> When Parrot operates on two strings (as in concatenation or comparison), they
+> must both use the same character set and encoding. Parrot will automatically
+> upgrade one or both of the strings to the next highest compatible format as
+> necessary. ASCII strings will automatically upgrade to UTF-8 strings if needed,
+> and UTF-8 will upgrade to UTF-16.  All of these conversions happen inside
+> Parrot, so the programmer doesn't need to worry about the details.
+635,639c668,675
+< <p><!--
+<       INDEX: Polymorphic Containers (PMCs)
+< --> <!--
+<       INDEX: PMCs (Polymorphic Containers)
+< --> Polymorphic Containers (PMCs) are the basis for complex data types and object&#45;oriented behavior in Parrot. In PIR, any variable that isn&#39;t a low&#45;level integer, number, or string is a PMC. PMC variables act much like the low&#45;level variables, but you have to instantiate a new PMC object before you use it. The <code>new</code> opcode creates a new PMC object of the specified type.</p>
+---
+> X<Polymorphic Containers (PMCs)>
+> X<PMCs (Polymorphic Containers)>
+> Polymorphic Containers (PMCs) are the basis for complex data types and
+> object-oriented behavior in Parrot. In PIR, any variable that isn't a
+> low-level integer, number, or string is a PMC. PMC variables act much
+> like the low-level variables, but you have to instantiate a new PMC
+> object before you use it. The C<new> opcode creates a new PMC object of
+> the specified type.
+644,648c680,687
+< <p>This example creates a <code>String</code> object, stores it in the PMC register variable <code>$P0</code>, assigns it the value &#34;That&#39;s a bollard and not a parrot&#34;, and prints it.</p>
+< 
+< <p>Every PMC has a type that indicates what data it can store and what behavior it supports. The <code>typeof</code><!--
+<       INDEX: typeof opcode
+< --> opcode reports the type of a PMC. When the result is a string variable, <code>typeof</code> returns the name of the type:</p>
+---
+> This example creates a C<String> object, stores it in the PMC register
+> variable C<$P0>, assigns it the value "That's a bollard and not a
+> parrot", and prints it.
+> 
+> Every PMC has a type that indicates what data it can store and what
+> behavior it supports. The C<typeof>X<typeof opcode> opcode reports the
+> type of a PMC.  When the result is a string variable, C<typeof> returns
+> the name of the type:
+653c692,693
+< <p>When the result is a PMC variable, <code>typeof</code> returns the <code>Class</code> PMC for that object type.</p>
+---
+> When the result is a PMC variable, C<typeof> returns the C<Class> PMC
+> for that object type.
+658,664c698,707
+< <p><!--
+<       INDEX: scalar PMCs
+< --> <!--
+<       INDEX: PMCs (Polymorphic Containers);scalar
+< --> In most of the examples shown so far, PMCs duplicate the behavior of integers, numbers, and strings. Parrot provides a set of PMCs for this exact purpose. <code>Integer</code>, <code>Float</code>, and <code>String</code> are thin overlays on Parrot&#39;s low&#45;level integers, numbers, and strings.</p>
+< 
+< <p>A previous example showed a string literal assigned to a PMC variable of type <code>String</code>. Direct assignment of a literal to a PMC works for all the low&#45;level types and their PMC equivalents:</p>
+---
+> X<scalar PMCs>
+> X<PMCs (Polymorphic Containers);scalar>
+> In most of the examples shown so far, PMCs duplicate the behavior of integers,
+> numbers, and strings. Parrot provides a set of PMCs for this exact purpose.
+> C<Integer>, C<Float>, and C<String> are thin overlays on Parrot's low-level
+> integers, numbers, and strings.
+> 
+> A previous example showed a string literal assigned to a PMC variable of type
+> C<String>. Direct assignment of a literal to a PMC works for all the low-level
+> types and their PMC equivalents:
+674,676c717
+< <p><!--
+<       INDEX: boxing
+< --></p>
+---
+> X<boxing>
+678c719,722
+< <p>You may also assign non&#45;constant low&#45;level integer, number, or string registers directly to a PMC. The PMC handles the conversion from the low&#45;level type to its own internal storage.This conversion of a simpler type to a more complex type is &#34;boxing&#34;.</p>
+---
+> You may also assign non-constant low-level integer, number, or string registers
+> directly to a PMC. The PMC handles the conversion from the low-level type to
+> its own internal storage.N<This conversion of a simpler type to a more complex
+> type is "boxing".>
+691c735,736
+< <p>The <code>box</code> opcode is a handy shortcut to create the appropriate PMC object from an integer, number, or string literal or variable.</p>
+---
+> The C<box> opcode is a handy shortcut to create the appropriate PMC
+> object from an integer, number, or string literal or variable.
+698,700c743,746
+< <p><!--
+<       INDEX: unboxing
+< --> In the reverse situation, when assigning a PMC to an integer, number, or string variable, the PMC also has the ability to convert its value to the low&#45;level type.The reverse of &#34;boxing&#34; is &#34;unboxing&#34;.</p>
+---
+> X<unboxing>
+> In the reverse situation, when assigning a PMC to an integer, number, or
+> string variable, the PMC also has the ability to convert its value to
+> the low-level type.N<The reverse of "boxing" is "unboxing".>
+716,724c762,768
+< <p>This example creates <code>Integer</code><!--
+<       INDEX: Integer PMC
+< -->, <code>Float</code><!--
+<       INDEX: Float PMC
+< -->, and <code>String</code><!--
+<       INDEX: String PMC
+< --> PMCs, and shows the effect of assigning each one back to a low&#45;level type.</p>
+< 
+< <p>Converting a string to an integer or number only makes sense when the contents of the string are a number. The <code>String</code> PMC will attempt to extract a number from the beginning of the string, but otherwise will return a false value.</p>
+---
+> This example creates C<Integer>X<Integer PMC>, C<Float>X<Float PMC>,
+> and C<String>X<String PMC> PMCs, and shows the effect of assigning each
+> one back to a low-level type.
+> 
+> Converting a string to an integer or number only makes sense when the contents
+> of the string are a number. The C<String> PMC will attempt to extract a number
+> from the beginning of the string, but otherwise will return a false value.
+729,733c773,778
+< <p><!--
+<       INDEX: aggregate PMCs
+< --> <!--
+<       INDEX: PMCs (Polymorphic Containers);aggregate
+< --> PMCs can define complex types that hold multiple values, commonly called aggregates. Two basic aggregate types are ordered arrays and associative arrays. The primary difference between these is that ordered arrays use integer keys for indexes and associative arrays use string keys.</p>
+---
+> X<aggregate PMCs>
+> X<PMCs (Polymorphic Containers);aggregate>
+> PMCs can define complex types that hold multiple values, commonly called
+> aggregates. Two basic aggregate types are ordered arrays and associative
+> arrays. The primary difference between these is that ordered arrays use integer
+> keys for indexes and associative arrays use string keys.
+735c780,781
+< <p>Aggregate PMCs support the use of numeric or string keys. PIR also offers a extensive set of operations for manipulating aggregate data types.</p>
+---
+> Aggregate PMCs support the use of numeric or string keys.  PIR also offers a
+> extensive set of operations for manipulating aggregate data types.
+740,748c786,809
+< <p><!--
+<       INDEX: arrays
+< --> <!--
+<       INDEX: ordered arrays
+< --> Parrot provides several ordered array PMCs, differentiated by whether the array should store booleans, integers, numbers, strings, or other PMCs, and whether the array should maintain a fixed size or dynamically resize for the number of elements it stores.</p>
+< 
+< <p>The core array types are <code>FixedPMCArray</code>, <code>ResizablePMCArray</code>, <code>FixedIntegerArray</code>, <code>ResizableIntegerArray</code>, <code>FixedFloatArray</code>, <code>ResizableFloatArray</code>, <code>FixedStringArray</code>, <code>ResizableStringArray</code>, <code>FixedBooleanArray</code>, and <code>ResizableBooleanArray</code>. The array types that start with &#34;Fixed&#34; have a fixed size and do not allow elements to be added outside their allocated size. The &#34;Resizable&#34; variants automatically extend themselves as more elements are added.With some additional overhead for checking array bounds and reallocating array memory. The array types that include &#34;String&#34;, &#34;Integer&#34;, or &#34;Boolean&#34; in the name use alternate packing methods for greater memory efficiency.</p>
+< 
+< <p>Parrot&#39;s core ordered array PMCs all have zero&#45;based integer keys. Extracting or inserting an element into the array uses PIR&#39;s standard key syntax, with the key in square brackets after the variable name. An lvalue key sets the value for that key. An rvalue key extracts the value for that key in the aggregate to use as the argument value:</p>
+---
+> X<arrays>
+> X<ordered arrays>
+> Parrot provides several ordered array PMCs, differentiated by whether
+> the array should store booleans, integers, numbers, strings, or other
+> PMCs, and whether the array should maintain a fixed size or dynamically
+> resize for the number of elements it stores.
+> 
+> The core array types are C<FixedPMCArray>, C<ResizablePMCArray>,
+> C<FixedIntegerArray>, C<ResizableIntegerArray>, C<FixedFloatArray>,
+> C<ResizableFloatArray>, C<FixedStringArray>, C<ResizableStringArray>,
+> C<FixedBooleanArray>, and C<ResizableBooleanArray>. The array
+> types that start with "Fixed" have a fixed size and do not allow
+> elements to be added outside their allocated size. The "Resizable"
+> variants automatically extend themselves as more elements are
+> added.N<With some additional overhead for checking array bounds and
+> reallocating array memory.> The array types that include "String",
+> "Integer", or "Boolean" in the name use alternate packing methods for
+> greater memory efficiency.
+> 
+> Parrot's core ordered array PMCs all have zero-based integer keys. Extracting
+> or inserting an element into the array uses PIR's standard key syntax, with the
+> key in square brackets after the variable name. An lvalue key sets the value
+> for that key.  An rvalue key extracts the value for that key in the aggregate
+> to use as the argument value:
+754c815,817
+< <p>Setting the array to an integer value directly (without a key) sets the number of elements of the array. Assigning an array directly to an integer retrieves the number of elements of the array.</p>
+---
+> Setting the array to an integer value directly (without a key) sets the number
+> of elements of the array.  Assigning an array directly to an integer retrieves
+> the number of elements of the array.
+758c821,822
+< <p>This is equivalent to using the <code>elements</code> opcode to retrieve the number of items currently in an array:</p>
+---
+> This is equivalent to using the C<elements> opcode to retrieve the number of
+> items currently in an array:
+761c825,829
+< <p>Some other useful instructions for working with ordered arrays are <code>push</code>, <code>pop</code>, <code>shift</code>, and <code>unshift</code>, to add or remove elements. <code>push</code> and <code>pop</code> work on the end of the array, the highest numbered index. <code>shift</code> and <code>unshift</code> work on the start of the array, adding or removing the zeroth element, and renumbering all the following elements.</p>
+---
+> Some other useful instructions for working with ordered arrays are
+> C<push>, C<pop>, C<shift>, and C<unshift>, to add or remove elements.
+> C<push> and C<pop> work on the end of the array, the highest numbered
+> index. C<shift> and C<unshift> work on the start of the array, adding or
+> removing the zeroth element, and renumbering all the following elements.
+771,777c839,847
+< <p><!--
+<       INDEX: associative arrays
+< --> <!--
+<       INDEX: hashes
+< --> <!--
+<       INDEX: dictionaries
+< --> An associative array is an unordered aggregate that uses string keys to identify elements. You may know them as &#34;hash tables&#34;, &#34;hashes&#34;, &#34;maps&#34;, or &#34;dictionaries&#34;. Parrot provides one core associative array PMC, called <code>Hash</code>. String keys work very much like integer keys. An lvalue key sets the value of an element, and an rvalue key extracts the value of an element. The string in the key must always be in single or double quotes.</p>
+---
+> X<associative arrays>
+> X<hashes>
+> X<dictionaries>
+> An associative array is an unordered aggregate that uses string keys to
+> identify elements.  You may know them as "hash tables", "hashes", "maps", or
+> "dictionaries". Parrot provides one core associative array PMC, called C<Hash>.
+> String keys work very much like integer keys.  An lvalue key sets the value of
+> an element, and an rvalue key extracts the value of an element. The string in
+> the key must always be in single or double quotes.
+782,784c852,854
+< <p>Assigning a <code>Hash</code><!--
+<       INDEX: Hash PMC
+< --> PMC (without a key) to an integer result fetches the number of elements in the hash.You may not set a <code>Hash</code> PMC directly to an integer value.</p>
+---
+> Assigning a C<Hash>X<Hash PMC> PMC (without a key) to an integer result
+> fetches the number of elements in the hash.N<You may not set a C<Hash>
+> PMC directly to an integer value.>
+787,789c857,860
+< <p>The <code>exists</code><!--
+<       INDEX: exists opcode
+< --> opcode tests whether a keyed value exists in an aggregate. It returns 1 if it finds the key in the aggregate and 0 otherwise. It doesn&#39;t care if the value itself is true or false, only that an entry exists for that key:</p>
+---
+> The C<exists>X<exists opcode> opcode tests whether a keyed value exists in an
+> aggregate. It returns 1 if it finds the key in the aggregate and 0 otherwise.
+> It doesn't care if the value itself is true or false, only that an entry exists
+> for that key:
+795,797c866,867
+< <p>The <code>delete</code><!--
+<       INDEX: delete opcode
+< --> opcode removes an element from an associative array:</p>
+---
+> The C<delete>X<delete opcode> opcode removes an element from an associative
+> array:
+803,807c873,878
+< <p><!--
+<       INDEX: iterators
+< --> <!--
+<       INDEX: PMCs (Polymorphic Containers); iterators
+< --> An iterator extracts values from an aggregate PMC one at a time. Iterators are most useful in loops which perform an action on every element in an aggregate. The <code>iter</code> opcode creates a new iterator from an aggregate PMC. It takes one argument, the PMC over which to iterate:</p>
+---
+> X<iterators>
+> X<PMCs (Polymorphic Containers); iterators>
+> An iterator extracts values from an aggregate PMC one at a time.  Iterators are
+> most useful in loops which perform an action on every element in an aggregate.
+> The C<iter> opcode creates a new iterator from an aggregate PMC. It takes one
+> argument, the PMC over which to iterate:
+810,812c881
+< <p>The <code>shift</code><!--
+<       INDEX: shift opcode
+< --> opcode extracts the next value from the iterator.</p>
+---
+> The C<shift>X<shift opcode> opcode extracts the next value from the iterator.
+815c884,885
+< <p>Evaluating the iterator PMC as a boolean returns whether the iterator has reached the end of the aggregate:</p>
+---
+> Evaluating the iterator PMC as a boolean returns whether the iterator has
+> reached the end of the aggregate:
+818,822c888,896
+< <p>Parrot provides predefined constants for working with iterators. <code>.ITERATE_FROM_START</code> and <code>.ITERATE_FROM_END</code> constants select whether an ordered array iterator starts from the beginning or end of the array. These two constants have no effect on associative array iterators, as their elements are unordered.</p>
+< 
+< <p>Load the iterator constants with the <code>.include</code><!--
+<       INDEX: .include directive
+< --> directive to include the file <em>iterator.pasm</em>. To use them, set the iterator PMC to the value of the constant:</p>
+---
+> Parrot provides predefined constants for working with iterators.
+> C<.ITERATE_FROM_START> and C<.ITERATE_FROM_END> constants select whether an
+> ordered array iterator starts from the beginning or end of the array.  These
+> two constants have no effect on associative array iterators, as their elements
+> are unordered.
+> 
+> Load the iterator constants with the C<.include>X<.include directive>
+> directive to include the file F<iterator.pasm>. To use them, set the
+> iterator PMC to the value of the constant:
+829c903,906
+< <p>With all of those separate pieces in one place, this example loads the iterator constants, creates an ordered array of &#34;a&#34;, &#34;b&#34;, &#34;c&#34;, creates an iterator from that array, and then loops over the iterator using a conditional <code>goto</code> to checks the boolean value of the iterator and another unconditional <code>goto</code>:</p>
+---
+> With all of those separate pieces in one place, this example loads the iterator
+> constants, creates an ordered array of "a", "b", "c", creates an iterator from
+> that array, and then loops over the iterator using a conditional C<goto> to
+> checks the boolean value of the iterator and another unconditional C<goto>:
+846c923,925
+< <p>Associative array iterators work similarly to ordered array iterators. When iterating over associative arrays, the <code>shift</code> opcode extracts keys instead of values. The key looks up the value in the original hash PMC.</p>
+---
+> Associative array iterators work similarly to ordered array iterators.  When
+> iterating over associative arrays, the C<shift> opcode extracts keys instead of
+> values. The key looks up the value in the original hash PMC.
+862c941,951
+< <p>This example creates an associative array <code>$P2</code> that contains three keys &#34;a&#34;, &#34;b&#34;, and &#34;c&#34;, assigning them the values 10, 20, and 30. It creates an iterator (<code>$P1</code>) from the associative array using the <code>iter</code> opcode, and then starts a loop over the iterator. At the start of each loop, the <code>unless</code> instruction checks whether the iterator has any more elements. If there are no more elements, <code>goto</code> jumps to the end of the loop, marked by the label <code>iter_end</code>. If there are more elements, the <code>shift</code> opcode extracts the next key. Keyed assignment stores the integer value of the element indexed by the key in <code>$I9</code>. After printing the integer value, <code>goto</code> jumps back to the start of the loop, marked by <code>iter_loop</code>.</p>
+---
+> This example creates an associative array C<$P2> that contains three
+> keys "a", "b", and "c", assigning them the values 10, 20, and 30. It
+> creates an iterator (C<$P1>) from the associative array using the
+> C<iter> opcode, and then starts a loop over the iterator. At the start
+> of each loop, the C<unless> instruction checks whether the iterator has
+> any more elements. If there are no more elements, C<goto> jumps to the
+> end of the loop, marked by the label C<iter_end>. If there are more
+> elements, the C<shift> opcode extracts the next key. Keyed assignment
+> stores the integer value of the element indexed by the key in C<$I9>.
+> After printing the integer value, C<goto> jumps back to the start of the
+> loop, marked by C<iter_loop>.
+867,871c956,962
+< <p><!--
+<       INDEX: keys
+< --> <!--
+<       INDEX: multi&#45;level keys
+< --> Aggregates can hold any data type, including other aggregates. Accessing elements deep within nested data structures is a common operation, so PIR provides a way to do it in a single instruction. Complex keys specify a series of nested data structures, with each individual key separated by a semicolon.</p>
+---
+> X<keys>
+> X<multi-level keys>
+> Aggregates can hold any data type, including other aggregates.
+> Accessing elements deep within nested data structures is a common
+> operation, so PIR provides a way to do it in a single instruction.
+> Complex keys specify a series of nested data structures, with each
+> individual key separated by a semicolon.
+881c972,975
+< <p>This example builds up a data structure of an associative array containing an ordered array. The complex key <code>[&#34;answer&#34;; $I1]</code> retrieves an element of the array within the hash. You can also set a value using a complex key:</p>
+---
+> This example builds up a data structure of an associative array
+> containing an ordered array. The complex key C<["answer"; $I1]>
+> retrieves an element of the array within the hash. You can also set a
+> value using a complex key:
+884c978,979
+< <p>The individual keys are integer or string literals, or variables with integer or string values.</p>
+---
+> The individual keys are integer or string literals, or variables with
+> integer or string values.
+889,891c984,989
+< <p><!--
+<       INDEX: PMCs (Polymorphic Containers); copying vs. cloning
+< --> PMC registers don&#39;t directly store the data for a PMC, they only store a pointer to the structure that stores the data. As a result, the <code>=</code> operator doesn&#39;t copy the entire PMC, it only copies the pointer to the PMC data. If you later modify the copy of the variable, it will also modify the original.</p>
+---
+> X<PMCs (Polymorphic Containers); copying vs. cloning>
+> PMC registers don't directly store the data for a PMC, they only store a
+> pointer to the structure that stores the data. As a result, the C<=>
+> operator doesn't copy the entire PMC, it only copies the pointer to the
+> PMC data. If you later modify the copy of the variable, it will also
+> modify the original.
+899c997,1000
+< <p>In this example, <code>$P0</code> and <code>$P1</code> are both pointers to the same internal data structure. Setting <code>$P1</code> to the string literal &#34;Zaphod&#34;, it overwrites the previous value &#34;Ford&#34;. Both <code>$P0</code> and <code>$P1</code> refer to the <code>String</code> PMC &#34;Zaphod&#34;.</p>
+---
+> In this example, C<$P0> and C<$P1> are both pointers to the same
+> internal data structure.  Setting C<$P1> to the string literal
+> "Zaphod", it overwrites the previous value "Ford". Both C<$P0> and
+> C<$P1> refer to the C<String> PMC "Zaphod".
+901,905c1002,1003
+< <p>The <code>clone</code> <!--
+<       INDEX: clone opcode
+< --> opcode makes a deep copy of a PMC, instead of copying the pointer like <code>=</code><!--
+<       INDEX: = operator
+< --> does.</p>
+---
+> The C<clone> X<clone opcode> opcode makes a deep copy of a PMC, instead
+> of copying the pointer like C<=>X<= operator> does.
+913,919c1011,1018
+< <p>This example creates an identical, independent clone of the PMC in <code>$P0</code> and puts it in <code>$P1</code>. Later changes to <code>$P0</code> have no effect on the PMC in <code>$P1</code>.With low&#45;level strings, the copies created by <code>clone</code> are copy&#45;on&#45;write<!--
+<       INDEX: copy&#45;on&#45;write
+< --> exactly the same as the copy created by <code>=</code>.</p>
+< 
+< <p>To assign the <i>value</i> of one PMC to another PMC that already exists, use the <code>assign</code><!--
+<       INDEX: assign opcode
+< --> opcode:</p>
+---
+> This example creates an identical, independent clone of the PMC in
+> C<$P0> and puts it in C<$P1>. Later changes to C<$P0> have no effect on
+> the PMC in C<$P1>.N<With low-level strings, the copies created by
+> C<clone> are copy-on-writeX<copy-on-write> exactly the same as the copy
+> created by C<=>.>
+> 
+> To assign the I<value> of one PMC to another PMC that already exists, use the
+> C<assign>X<assign opcode> opcode:
+928c1027,1032
+< <p>This example creates two <code>Integer</code> PMCs, <code>$P1</code> and <code>$P2</code>, and gives the first one the value 42. It then uses <code>assign</code> to pass the same integer value on to <code>$P1</code>. Though <code>$P0</code> increments, <code>$P1</code> doesn&#39;t change. The result for <code>assign</code> must have an existing object of the right type in it, because <code>assign</code> neither creates a new duplicate object (as does <code>clone</code>) or reuses the source object (as does <code>=</code>).</p>
+---
+> This example creates two C<Integer> PMCs, C<$P1> and C<$P2>, and gives the
+> first one the value 42. It then uses C<assign> to pass the same integer value
+> on to C<$P1>. Though C<$P0> increments, C<$P1> doesn't change. The result for
+> C<assign> must have an existing object of the right type in it, because
+> C<assign> neither creates a new duplicate object (as does C<clone>) or reuses
+> the source object (as does C<=>).
+933,937c1037,1038
+< <p><!--
+<       INDEX: properties
+< --> <!--
+<       INDEX: PMCs (Polymorphic Containers); properties
+< --></p>
+---
+> X<properties>
+> X<PMCs (Polymorphic Containers); properties>
+939c1040,1041
+< <p>PMCs can have additional values attached to them as &#34;properties&#34; of the PMC. Most properties hold extra metadata about the PMC.</p>
+---
+> PMCs can have additional values attached to them as "properties" of the
+> PMC. Most properties hold extra metadata about the PMC.
+941,943c1043,1045
+< <p>The <code>setprop</code><!--
+<       INDEX: setprop opcode
+< --> opcode sets the value of a named property on a PMC. It takes three arguments: the PMC on which to set a property, the name of the property, and a PMC containing the value of the property.</p>
+---
+> The C<setprop>X<setprop opcode> opcode sets the value of a named property on a
+> PMC. It takes three arguments: the PMC on which to set a property, the name of
+> the property, and a PMC containing the value of the property.
+946,948c1048,1050
+< <p>The <code>getprop</code><!--
+<       INDEX: getprop opcode
+< --> opcode returns the value of a property. It takes two arguments: the name of the property and the PMC from which to retrieve the property value.</p>
+---
+> The C<getprop>X<getprop opcode> opcode returns the value of a property.  It
+> takes two arguments: the name of the property and the PMC from which to
+> retrieve the property value.
+951c1053,1056
+< <p>This example creates a <code>String</code> object in <code>$P0</code> and an <code>Integer</code> object with the value 1 in <code>$P1</code>. <code>setprop</code> sets a property named &#34;eric&#34; on the object in <code>$P0</code> and gives the property the value of <code>$P1</code>. <code>getprop</code> retrieves the value of the property &#34;eric&#34; on <code>$P0</code> and stores it in <code>$P2</code>.</p>
+---
+> This example creates a C<String> object in C<$P0> and an C<Integer> object with
+> the value 1 in C<$P1>. C<setprop> sets a property named "eric" on the object in
+> C<$P0> and gives the property the value of C<$P1>. C<getprop> retrieves the
+> value of the property "eric" on C<$P0> and stores it in C<$P2>.
+962c1067,1068
+< <p>Parrot stores PMC properties in an associative array where the name of the property is the key.</p>
+---
+> Parrot stores PMC properties in an associative array where the name of the
+> property is the key.
+964,966c1070
+< <p><code>delprop</code><!--
+<       INDEX: delprop opcode
+< --> deletes a property from a PMC.</p>
+---
+> C<delprop>X<delprop opcode> deletes a property from a PMC.
+969,971c1073,1074
+< <p>You can fetch a complete hash of all properties on a PMC with <code>prophash</code><!--
+<       INDEX: prophash opcode
+< -->:</p>
+---
+> You can fetch a complete hash of all properties on a PMC with
+> C<prophash>X<prophash opcode>:
+974c1077
+< <p>Fetching the value of a non&#45;existent property returns an <code>Undef</code> PMC.</p>
+---
+> Fetching the value of a non-existent property returns an C<Undef> PMC.
+979,991c1082,1104
+< <p><!--
+<       INDEX: vtable functions
+< --> You may have noticed that a simple operation sometimes has a different effect on different PMCs. Assigning a low&#45;level integer value to a <code>Integer</code> PMC sets its integer value of the PMC, but assigning that same integer to an ordered array sets the size of the array.</p>
+< 
+< <p>Every PMC defines a standard set of low&#45;level operations called vtable functions. When you perform an assignment like:</p>
+< 
+< <pre>   $P0 = 5</pre>
+< 
+< <p>... Parrot calls the <code>set_integer_native</code> vtable function on the PMC referred to by register <code>$P0</code>.</p>
+< 
+< <p><!--
+<       INDEX: polymorphic substitution
+< --> Parrot has a fixed set of vtable functions, so that any PMC can stand in for any other PMC; they&#39;re polymorphic.Hence the name &#34;Polymorphic Container&#34;. Every PMC defines some behavior for every vtable function. The default behavior is to throw an exception reporting that the PMC doesn&#39;t implement that vtable function. The full set of vtable functions for a PMC defines the PMC&#39;s basic interface, but PMCs may also define methods to extend their behavior beyond the vtable set.</p>
+---
+> X<vtable functions>
+> You may have noticed that a simple operation sometimes has a different effect
+> on different PMCs. Assigning a low-level integer value to a C<Integer> PMC sets
+> its integer value of the PMC, but assigning that same integer to an ordered
+> array sets the size of the array.
+> 
+> Every PMC defines a standard set of low-level operations called vtable
+> functions. When you perform an assignment like:
+> 
+>    $P0 = 5
+> 
+> 
+> ... Parrot calls the C<set_integer_native> vtable function on the PMC referred
+> to by register C<$P0>.
+> 
+> X<polymorphic substitution>
+> Parrot has a fixed set of vtable functions, so that any PMC can stand in for
+> any other PMC; they're polymorphic.N<Hence the name "Polymorphic Container".>
+> Every PMC defines some behavior for every vtable function. The default behavior
+> is to throw an exception reporting that the PMC doesn't implement that vtable
+> function. The full set of vtable functions for a PMC defines the PMC's basic
+> interface, but PMCs may also define methods to extend their behavior beyond the
+> vtable set.
+996,1006c1109,1120
+< <p><!--
+<       INDEX: namespaces
+< --> <!--
+<       INDEX: global variables
+< --> Parrot performs operations on variables stored in small register sets local to each subroutine. For more complex tasks,...and for most high&#45;level languages that Parrot supports. it&#39;s also useful to have variables that live beyond the scope of a single subroutine. These variables may be global to the entire program or restricted to a particular library. Parrot stores long&#45;lived variables in a hierarchy of namespaces.</p>
+< 
+< <p>The opcodes <code>set_global</code><!--
+<       INDEX: set_global opcode
+< --> and <code>get_global</code><!--
+<       INDEX: get_global opcode
+< --> store and fetch a variable in a namespace:</p>
+---
+> X<namespaces>
+> X<global variables>
+> Parrot performs operations on variables stored in small register sets local to
+> each subroutine. For more complex tasks,N<...and for most high-level languages
+> that Parrot supports.> it's also useful to have variables that live beyond the
+> scope of a single subroutine. These variables may be global to the entire
+> program or restricted to a particular library. Parrot stores long-lived
+> variables in a hierarchy of namespaces.
+> 
+> The opcodes C<set_global>X<set_global opcode> and
+> C<get_global>X<get_global opcode> store and fetch a variable in a
+> namespace:
+1014,1018c1128,1144
+< <p>The first two statements in this example create a <code>String</code> PMC in <code>$P0</code> and assign it a value. In the third statement, <code>set_global</code> stores that PMC as the named global variable <code>bee</code>. At some later point in the program, <code>get_global</code> retrieves the global variable by name, and stores it in <code>$P1</code> to print.</p>
+< 
+< <p>Namespaces can only store PMC variables. Parrot boxes all primitive integer, number, or string values into the corresponding PMCs before storing them in a namespace.</p>
+< 
+< <p>The name of every variable stored in a particular namespace must be unique. You can&#39;t have store both an <code>Integer</code> PMC and an array PMC both named &#34;bee&#34;, stored in the same namespace.You may wonder why anyone would want to do this. We wonder the same thing, but Perl 5 does it all the time. The Perl 6 implementation on Parrot includes type sigils in the names of the variables it stores in namespaces so each name is unique, e.g. <code>$bee</code>, <code>@bee</code>....</p>
+---
+> The first two statements in this example create a C<String> PMC in
+> C<$P0> and assign it a value. In the third statement, C<set_global>
+> stores that PMC as the named global variable C<bee>.  At some later
+> point in the program, C<get_global> retrieves the global variable by
+> name, and stores it in C<$P1> to print.
+> 
+> Namespaces can only store PMC variables.  Parrot boxes all primitive integer,
+> number, or string values into the corresponding PMCs before storing them in a
+> namespace.
+> 
+> The name of every variable stored in a particular namespace must be
+> unique. You can't have store both an C<Integer> PMC and an array PMC
+> both named "bee", stored in the same namespace.N<You may wonder why
+> anyone would want to do this. We wonder the same thing, but Perl 5 does
+> it all the time. The Perl 6 implementation on Parrot includes type
+> sigils in the names of the variables it stores in namespaces so each
+> name is unique, e.g. C<$bee>, C<@bee>....>
+1023,1027c1149,1150
+< <p><!--
+<       INDEX: hierarchical namespaces
+< --> <!--
+<       INDEX: namespaces; hierarchy
+< --></p>
+---
+> X<hierarchical namespaces>
+> X<namespaces; hierarchy>
+1029,1031c1152,1162
+< <p>A single global namespace would be far too limiting for most languages or applications. The risk of accidental collisions &#45;&#45; where two libraries try to use the same name for some variable &#45;&#45; would be quite high for larger code bases. Parrot maintains a collection of namespaces arranged as a tree, with the <code>parrot</code> namespace as the root. Every namespace you declare is a child of the <code>parrot</code> namespace (or a child of a child....).</p>
+< 
+< <p>The <code>set_global</code> and <code>get_global</code> opcodes both have alternate forms that take a key name to access a variable in a particular namespace within the tree. This code example stores a variable as <code>bill</code> in the Duck namespace and retrieves it again:</p>
+---
+> A single global namespace would be far too limiting for most languages or
+> applications. The risk of accidental collisions -- where two libraries try to
+> use the same name for some variable -- would be quite high for larger code
+> bases. Parrot maintains a collection of namespaces arranged as a tree, with the
+> C<parrot> namespace as the root.  Every namespace you declare is a child of the
+> C<parrot> namespace (or a child of a child....).
+> 
+> The C<set_global> and C<get_global> opcodes both have alternate forms that take
+> a key name to access a variable in a particular namespace within the tree. This
+> code example stores a variable as C<bill> in the Duck namespace and retrieves
+> it again:
+1035c1166,1168
+< <p>The key name for the namespace can have multiple levels, which correspond to levels in the namespace hierarchy. This example stores a variable as <code>bill</code> in the Electric namespace under the General namespace in the hierarchy.</p>
+---
+> The key name for the namespace can have multiple levels, which correspond to
+> levels in the namespace hierarchy. This example stores a variable as C<bill> in
+> the Electric namespace under the General namespace in the hierarchy.
+1039,1043c1172,1173
+< <p><!--
+<       INDEX: root namespace
+< --> <!--
+<       INDEX: namespaces; root
+< --></p>
+---
+> X<root namespace>
+> X<namespaces; root>
+1045,1047c1175,1181
+< <p>The <code>set_global</code> and <code>get_global</code> opcode operate on the currently selected namespace. The default top&#45;level namespace is the &#34;root&#34; namespace. The <code>.namespace</code><!--
+<       INDEX: .namespace directive
+< --> directive allows you to declare any namespace for subsequent code. If you select the General Electric namespace, then store or retrieve the <code>bill</code> variable without specifying a namespace, you will work with the General Electric bill, not the Duck bill.</p>
+---
+> The C<set_global> and C<get_global> opcode operate on the currently selected
+> namespace. The default top-level namespace is the "root" namespace. The
+> C<.namespace>X<.namespace directive> directive allows you to declare any
+> namespace for subsequent code.  If you select the General Electric
+> namespace, then store or retrieve the C<bill> variable without
+> specifying a namespace, you will work with the General Electric bill,
+> not the Duck bill.
+1049c1183
+< <pre>  .namespace [&#34;General&#34;;&#34;Electric&#34;]
+---
+>   .namespace ["General";"Electric"]
+1051,1052c1185,1191
+<   set_global &#34;bill&#34;, $P0
+<   $P1 = get_global &#34;bill&#34;</pre>
+---
+>   set_global "bill", $P0
+>   $P1 = get_global "bill"
+> 
+> 
+> Passing an empty key to the C<.namespace> directive resets the selected
+> namespace to the root namespace. The brackets are required even when the
+> key is empty.
+1054c1193
+< <p>Passing an empty key to the <code>.namespace</code> directive resets the selected namespace to the root namespace. The brackets are required even when the key is empty.</p>
+---
+>   .namespace [ ]
+1056d1194
+< <pre>  .namespace [ ]</pre>
+1058,1062c1196,1202
+< <p>When you need to be absolutely sure you&#39;re working with the root namespace regardless of what namespace is currently active, use the <code>set_root_global</code><!--
+<       INDEX: set_root_global opcode
+< --> and <code>get_root_global</code><!--
+<       INDEX: get_root_global opcode
+< --> opcodes instead of <code>set_global</code> and <code>get_global</code>. This example sets and retrieves the variable <code>bill</code> in the Dollar namespace, which is directly under the root namespace:</p>
+---
+> When you need to be absolutely sure you're working with the root namespace
+> regardless of what namespace is currently active, use the
+> C<set_root_global>X<set_root_global opcode> and
+> C<get_root_global>X<get_root_global opcode> opcodes instead of
+> C<set_global> and C<get_global>. This example sets and retrieves the
+> variable C<bill> in the Dollar namespace, which is directly under the
+> root namespace:
+1066,1080c1206,1222
+< <p><!--
+<       INDEX: HLL namespaces
+< --> <!--
+<       INDEX: namespaces; hll
+< --> To prevent further collisions, each high&#45;level language running on Parrot operates within its own virtual namespace root. The default virtual root is <code>parrot</code>, and the <code>.HLL</code><!--
+<       INDEX: .HLL directive
+< --> directive (for <i>H</i>igh&#45;<i>L</i>evel <i>L</i>anguage) selects an alternate virtual root for a particular high&#45;level language:</p>
+< 
+< <pre>  .HLL &#39;ruby&#39;</pre>
+< 
+< <p>The <code>set_hll_global</code><!--
+<       INDEX: set_hll_global opcode
+< --> and <code>get_hll_global</code><!--
+<       INDEX: get_hll_global opcode
+< --> opcodes are like <code>set_root_global</code> and <code>get_root_global</code>, except they always operate on the virtual root for the currently selected HLL. This example stores and retrieves a <code>bill</code> variable in the Euro namespace, under the Dutch HLL namespace root:</p>
+---
+> X<HLL namespaces>
+> X<namespaces; hll>
+> To prevent further collisions, each high-level language running on
+> Parrot operates within its own virtual namespace root. The default
+> virtual root is C<parrot>, and the C<.HLL>X<.HLL directive> directive
+> (for I<H>igh-I<L>evel I<L>anguage) selects an alternate virtual root for
+> a particular high-level language:
+> 
+>   .HLL 'ruby'
+> 
+> 
+> The C<set_hll_global>X<set_hll_global opcode> and
+> C<get_hll_global>X<get_hll_global opcode> opcodes are like
+> C<set_root_global> and C<get_root_global>, except they always operate on
+> the virtual root for the currently selected HLL. This example stores and
+> retrieves a C<bill> variable in the Euro namespace, under the Dutch HLL
+> namespace root:
+1082c1224
+< <pre>  .HLL &#39;Dutch&#39;
+---
+>   .HLL 'Dutch'
+1084,1085c1226,1228
+<   set_hll_global [&#34;Euro&#34;], &#34;bill&#34;, $P0
+<   $P1 = get_hll_global [&#34;Euro&#34;], &#34;bill&#34;</pre>
+---
+>   set_hll_global ["Euro"], "bill", $P0
+>   $P1 = get_hll_global ["Euro"], "bill"
+> 
+1090,1094c1233,1251
+< <p><!--
+<       INDEX: NameSpace PMC
+< --> Namespaces are just PMCs. They implement the standard vtable functions and a few extra methods. The <code>get_namespace</code><!--
+<       INDEX: get_namespace opcode
+< --> opcode retrieves the currently selected namespace as a PMC object:</p>
+---
+> X<NameSpace PMC>
+> Namespaces are just PMCs. They implement the standard vtable functions
+> and a few extra methods. The C<get_namespace>X<get_namespace opcode>
+> opcode retrieves the currently selected namespace as a PMC object:
+> 
+>   $P0 = get_namespace
+> 
+> 
+> The C<get_root_namespace>X<get_root_namespace opcode> opcode retrieves
+> the namespace object for the root namespace.  The
+> C<get_hll_namespace>X<get_hll_namespace opcode> opcode retrieves the
+> virtual root for the currently selected HLL.
+> 
+>   $P0 = get_root_namespace
+>   $P0 = get_hll_namespace
+> 
+> 
+> Each of these three opcodes can take a key argument to retrieve a namespace
+> under the currenly selected namespace, root namespace, or HLL root namespace:
+1096c1253,1255
+< <pre>  $P0 = get_namespace</pre>
+---
+>   $P0 = get_namespace ["Duck"]
+>   $P0 = get_root_namespace ["General";"Electric"]
+>   $P0 = get_hll_namespace ["Euro"]
+1098,1102d1256
+< <p>The <code>get_root_namespace</code><!--
+<       INDEX: get_root_namespace opcode
+< --> opcode retrieves the namespace object for the root namespace. The <code>get_hll_namespace</code><!--
+<       INDEX: get_hll_namespace opcode
+< --> opcode retrieves the virtual root for the currently selected HLL.</p>
+1104,1105c1258,1261
+< <pre>  $P0 = get_root_namespace
+<   $P0 = get_hll_namespace</pre>
+---
+> Once you have a namespace object you can use it to retrieve variables from the
+> namespace instead of using a keyed lookup. This example first looks up the Euro
+> namespace in the currently selected HLL, then retrieves the C<bill> variable
+> from that namespace:
+1107c1263,1264
+< <p>Each of these three opcodes can take a key argument to retrieve a namespace under the currenly selected namespace, root namespace, or HLL root namespace:</p>
+---
+>   $P0 = get_hll_namespace ["Euro"]
+>   $P1 = get_global $P0, "bill"
+1109,1111d1265
+< <pre>  $P0 = get_namespace [&#34;Duck&#34;]
+<   $P0 = get_root_namespace [&#34;General&#34;;&#34;Electric&#34;]
+<   $P0 = get_hll_namespace [&#34;Euro&#34;]</pre>
+1113c1267,1270
+< <p>Once you have a namespace object you can use it to retrieve variables from the namespace instead of using a keyed lookup. This example first looks up the Euro namespace in the currently selected HLL, then retrieves the <code>bill</code> variable from that namespace:</p>
+---
+> Namespaces also provide a set of methods to provide more complex
+> behavior than the standard vtable functions allow. The
+> C<get_name>X<get_name method> method returns the name of the namespace
+> as a C<ResizableStringArray>:
+1115,1116c1272
+< <pre>  $P0 = get_hll_namespace [&#34;Euro&#34;]
+<   $P1 = get_global $P0, &#34;bill&#34;</pre>
+---
+>   $P3 = $P0.'get_name'()
+1118,1120d1273
+< <p>Namespaces also provide a set of methods to provide more complex behavior than the standard vtable functions allow. The <code>get_name</code><!--
+<       INDEX: get_name method
+< --> method returns the name of the namespace as a <code>ResizableStringArray</code>:</p>
+1122c1275,1276
+< <pre>  $P3 = $P0.&#39;get_name&#39;()</pre>
+---
+> The C<get_parent>X<get_parent method> method retrieves a namespace
+> object for the parent namespace that contains this one:
+1124,1126c1278
+< <p>The <code>get_parent</code><!--
+<       INDEX: get_parent method
+< --> method retrieves a namespace object for the parent namespace that contains this one:</p>
+---
+>   $P5 = $P0.'get_parent'()
+1128d1279
+< <pre>  $P5 = $P0.&#39;get_parent&#39;()</pre>
+1130,1132c1281,1282
+< <p>The <code>get_class</code><!--
+<       INDEX: get_class method
+< --> method retrieves any Class PMC associated with the namespace:</p>
+---
+> The C<get_class>X<get_class method> method retrieves any Class PMC
+> associated with the namespace:
+1134c1284
+< <pre>  $P6 = $P0.&#39;get_class&#39;()</pre>
+---
+>   $P6 = $P0.'get_class'()
+1136,1140d1285
+< <p>The <code>add_var</code><!--
+<       INDEX: add_var method
+< --> and <code>find_var</code><!--
+<       INDEX: find_var method
+< --> methods store and retrieve variables in a namespace in a language&#45;neutral way:</p>
+1142,1143c1287,1289
+< <pre>  $P0.&#39;add_var&#39;(&#34;bee&#34;, $P3)
+<   $P1 = $P0.&#39;find_var&#39;(&#34;bee&#34;)</pre>
+---
+> The C<add_var>X<add_var method> and C<find_var>X<find_var method>
+> methods store and retrieve variables in a namespace in a
+> language-neutral way:
+1145,1147c1291,1292
+< <p>The <code>find_namespace</code><!--
+<       INDEX: find_namespace method
+< --> method looks up a namespace, just like the <code>get_namespace</code> opcode:</p>
+---
+>   $P0.'add_var'("bee", $P3)
+>   $P1 = $P0.'find_var'("bee")
+1149d1293
+< <pre>  $P1 = $P0.&#39;find_namespace&#39;(&#34;Duck&#34;)</pre>
+1151,1153c1295,1296
+< <p>The <code>add_namespace</code><!--
+<       INDEX: add_namespace method
+< --> method adds a new namespace as a child of the namespace object:</p>
+---
+> The C<find_namespace>X<find_namespace method> method looks up a
+> namespace, just like the C<get_namespace> opcode:
+1155c1298
+< <pre>  $P0.&#39;add_namespace&#39;($P1)</pre>
+---
+>   $P1 = $P0.'find_namespace'("Duck")
+1157,1159d1299
+< <p>The <code>make_namespace</code><!--
+<       INDEX: make_namespace method
+< --> method looks up a namespace as a child of the namespace object and returns it. If the requested namespace doesn&#39;t exist, <code>make_namespace</code> creates a new one and adds it under that name:</p>
+1161c1301,1313
+< <pre>  $P1 = $P0.&#39;make_namespace&#39;(&#34;Duck&#34;)</pre>
+---
+> The C<add_namespace>X<add_namespace method> method adds a new namespace
+> as a child of the namespace object:
+> 
+>   $P0.'add_namespace'($P1)
+> 
+> 
+> The C<make_namespace>X<make_namespace method> method looks up a
+> namespace as a child of the namespace object and returns it. If the
+> requested namespace doesn't exist, C<make_namespace> creates a new one
+> and adds it under that name:
+> 
+>   $P1 = $P0.'make_namespace'("Duck")
+> 
+1166,1168c1318,1322
+< <p><!--
+<       INDEX: aliasing
+< --> Just like regular assignment, the various operations to store a variable in a namespace only store a pointer to the PMC. If you modify the local PMC after storing in a namespace, those changes will also appear in the stored global. To store a true copy of the PMC, <code>clone</code> it before you store it.</p>
+---
+> X<aliasing>
+> Just like regular assignment, the various operations to store a variable in a
+> namespace only store a pointer to the PMC. If you modify the local PMC after
+> storing in a namespace, those changes will also appear in the stored global. To
+> store a true copy of the PMC, C<clone> it before you store it.
+1170c1324,1325
+< <p>Leaving the global variable as an alias for a local variable has its advantages. If you retrieve a stored global into a register and modify it:</p>
+---
+> Leaving the global variable as an alias for a local variable has its advantages.
+> If you retrieve a stored global into a register and modify it:
+1174c1329,1330
+< <p>... you modify the value of the stored global, so you don&#39;t need to call <code>set_global</code> again.</p>
+---
+> ... you modify the value of the stored global, so you don't need to call
+> C<set_global> again.
+1178c1334
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch05_control_structures.pod.html parrot/docs/html/docs/book/pir/ch05_control_structures.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Control Structures
+---
+>                     Control Structures
+302c302
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch06_subroutines.pod.html parrot/docs/html/docs/book/pir/ch06_subroutines.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Subroutines
+---
+>                     Subroutines
+759c759
+< --> Native Call Interface (NCI) is a special version of the Parrot calling conventions for calling functions in shared C libraries with a known signature. This is a simplified version of the first test in <em><a href="../../../t/pmc/nci.t.html">t/pmc/nci.t</a></em>:</p>
+---
+> --> Native Call Interface (NCI) is a special version of the Parrot calling conventions for calling functions in shared C libraries with a known signature. This is a simplified version of the first test in <em>t/pmc/nci.t</em>:</p>
+789c789
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch07_objects.pod.html parrot/docs/html/docs/book/pir/ch07_objects.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Classes and Objects
+---
+>                     Classes and Objects
+341c341
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch08_io.pod.html parrot/docs/html/docs/book/pir/ch08_io.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; I/O
+---
+>                     I/O
+368c368
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/book/pir/ch09_exceptions.pod.html parrot/docs/html/docs/book/pir/ch09_exceptions.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; Exceptions
+---
+>                     Exceptions
+277c277
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/compiler_faq.pod.html parrot/docs/html/docs/compiler_faq.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Parrot FAQ for compiler writers in PIR
+---
+>                     Parrot FAQ for compiler writers in PIR
+302c302
+< See also <em><a href="../t/dynpmc/dynlexpad.t.html">t/dynpmc/dynlexpad.t</a></em>.</p>
+---
+> See also <em>t/dynpmc/dynlexpad.t</em>.</p>
+636c636
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/configuration.pod.html parrot/docs/html/docs/configuration.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; Parrot Configuration System
+---
+>                     Parrot Configuration System
+55c55
+< you would add the code used to determine its size in <em><a href="../config/auto/sizes.pm.html">config/auto/sizes.pm</a></em>.
+---
+> you would add the code used to determine its size in <em>config/auto/sizes.pm</em>.
+83c83
+< To enable them run <em><a href="../Configure.pl.html">Configure.pl</a></em> with the <code>&#45;&#45;ask</code> option.</p>
+---
+> To enable them run <em>Configure.pl</em> with the <code>&#45;&#45;ask</code> option.</p>
+118,119c118,119
+< the <em><a href="../Configure.pl.html">Configure.pl</a></em> script.
+< The system is invoked by instantiating a <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object,
+---
+> the <em>Configure.pl</em> script.
+> The system is invoked by instantiating a <a href='TODO'>Parrot::Configure</a> object,
+131c131
+< the step <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em> uses the <code>init::defaults</code> namespace.</p>
+---
+> the step <em>config/init/defaults.pm</em> uses the <code>init::defaults</code> namespace.</p>
+133c133
+< <p>Each step inherits its constructor and some other methods from <em><a href="../lib/Parrot/Configure/Step.pm.html">lib/Parrot/Configure/Step.pm</a></em>.
+---
+> <p>Each step inherits its constructor and some other methods from <em>lib/Parrot/Configure/Step.pm</em>.
+167c167
+< <p>The configuration system won&#39;t execute your step by default unless it&#39;s specifically told to. To do this, edit <em><a href="../lib/Parrot/Configure/Step/List.pm.html">lib/Parrot/Configure/Step/List.pm</a></em>. Steps are run in the order in which that are registered with the <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object.</p>
+---
+> <p>The configuration system won&#39;t execute your step by default unless it&#39;s specifically told to. To do this, edit <em>lib/Parrot/Configure/Step/List.pm</em>. Steps are run in the order in which that are registered with the <a href='TODO'>Parrot::Configure</a> object.</p>
+169c169
+< <p>Various utility functions for configuration steps are provided by the <a href='..%2Flib%2FParrot%2FConfigure%2FUtils.pm.html'>Parrot::Configure::Utils</a> module.</p>
+---
+> <p>Various utility functions for configuration steps are provided by the <a href='TODO'>Parrot::Configure::Utils</a> module.</p>
+210c210
+< <p>Command&#45;line arguments are now processed by <code>process_options()</code>, a subroutine exported by <a href='..%2Flib%2FParrot%2FConfigure%2FOptions.pm.html'>Parrot::Configure::Options</a>. If you add a new option, don&#39;t forget to add it to this documentation and to appropriate locations. Most options should be added to <code>@shared_valid_options</code> in <em><a href="../lib/Parrot/Configure/Options/Conf/Shared.pm.html">lib/Parrot/Configure/Options/Conf/Shared.pm</a></em>.</p>
+---
+> <p>Command&#45;line arguments are now processed by <code>process_options()</code>, a subroutine exported by <a href='TODO'>Parrot::Configure::Options</a>. If you add a new option, don&#39;t forget to add it to this documentation and to appropriate locations. Most options should be added to <code>@shared_valid_options</code> in <em>lib/Parrot/Configure/Options/Conf/Shared.pm</em>.</p>
+212c212
+< <p>Arguments passed to <em><a href="../Configure.pl.html">Configure.pl</a></em> are held in a <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> object stored inside the <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object. The options data object may be accessed via the <code>Parrot::Configure::options()</code> method.</p>
+---
+> <p>Arguments passed to <em>Configure.pl</em> are held in a <a href='TODO'>Parrot::Configure::Data</a> object stored inside the <a href='TODO'>Parrot::Configure</a> object. The options data object may be accessed via the <code>Parrot::Configure::options()</code> method.</p>
+217c217
+< <p>As an alternative to typing a long string of options on the command&#45;line, Parrot can now be configured from a configuration file. You put the options in a configuration file, then call <em><a href="../Configure.pl.html">Configure.pl</a></em> as follows:</p>
+---
+> <p>As an alternative to typing a long string of options on the command&#45;line, Parrot can now be configured from a configuration file. You put the options in a configuration file, then call <em>Configure.pl</em> as follows:</p>
+228c228
+< <p>The second step is <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em>, which sets up some defaults in a <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> object contained by the main <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object. It can be accessed via the <code>Parrot::Configure::data()</code> method. You get and set configuration system&#39;s data by interacting with this object. Some of its methods are summarized below.</p>
+---
+> <p>The second step is <em>config/init/defaults.pm</em>, which sets up some defaults in a <a href='TODO'>Parrot::Configure::Data</a> object contained by the main <a href='TODO'>Parrot::Configure</a> object. It can be accessed via the <code>Parrot::Configure::data()</code> method. You get and set configuration system&#39;s data by interacting with this object. Some of its methods are summarized below.</p>
+245c245
+< Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system&#39;s data.See the <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> documentation for further details.</dl>
+---
+> Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system&#39;s data.See the <a href='TODO'>Parrot::Configure::Data</a> documentation for further details.</dl>
+261c261
+< These settings are deleted before <em><a href="../lib/Parrot/Config.pm.html">lib/Parrot/Config.pm</a></em> is written. These entries are only used e.g. for Makefile creation.</dl>
+---
+> These settings are deleted before <em>lib/Parrot/Config.pm</em> is written. These entries are only used e.g. for Makefile creation.</dl>
+266c266
+< <p>Parrot configuration is currently jump&#45;started by extracting considerable information from variables associated with the instance of Perl 5 which the user is using to run <em><a href="../Configure.pl.html">Configure.pl</a></em>. These variables are largely looked up in the <code>%Config</code> found in the Perl 5 <em>Config.pm</em>, but may also be sought in Perl 5 special variables such as <code>$^O</code>. All such lookups should be done in configuration step <code>init::defaults</code> and <b>only</b> in that step. Special accessors are available for working with such variables; see <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em> and <em><a href="../lib/Parrot/Configure/Data.pm.html">lib/Parrot/Configure/Data.pm</a></em>.</p>
+---
+> <p>Parrot configuration is currently jump&#45;started by extracting considerable information from variables associated with the instance of Perl 5 which the user is using to run <em>Configure.pl</em>. These variables are largely looked up in the <code>%Config</code> found in the Perl 5 <em>Config.pm</em>, but may also be sought in Perl 5 special variables such as <code>$^O</code>. All such lookups should be done in configuration step <code>init::defaults</code> and <b>only</b> in that step. Special accessors are available for working with such variables; see <em>config/init/defaults.pm</em> and <em>lib/Parrot/Configure/Data.pm</em>.</p>
+276c276
+< <p><a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a>, <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a>, <a href='..%2Flib%2FParrot%2FConfigure%2FUtils.pm.html'>Parrot::Configure::Utils</a>, <a href='..%2Flib%2FParrot%2FConfigure%2FStep.pm.html'>Parrot::Configure::Step</a></p>
+---
+> <p><a href='TODO'>Parrot::Configure</a>, <a href='TODO'>Parrot::Configure::Data</a>, <a href='TODO'>Parrot::Configure::Utils</a>, <a href='TODO'>Parrot::Configure::Step</a></p>
+280c280
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/debugger.pod.html parrot/docs/html/docs/debugger.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; The Parrot Debugger
+---
+>                     The Parrot Debugger
+307c307
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/debug.pod.html parrot/docs/html/docs/debug.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; Debugging Parrot
+---
+>                     Debugging Parrot
+76c76
+< <p>See <em><a href="dev/infant.pod.html">docs/dev/infant.pod</a></em> for details of one frequent problem: infant mortality. Infant mortality is when you create a Parrot object, but the garbage collector runs before you put it into a Parrot register or in something else that is itself within a Parrot register.</p>
+---
+> <p>See <em>docs/dev/infant.pod</em> for details of one frequent problem: infant mortality. Infant mortality is when you create a Parrot object, but the garbage collector runs before you put it into a Parrot register or in something else that is itself within a Parrot register.</p>
+88c88
+< <p>One possible tool is <code>parrot_debugger</code>, the Parrot Debugger. See <em><a href="debugger.pod.html">docs/debugger.pod</a></em> for details on it.</p>
+---
+> <p>One possible tool is <code>parrot_debugger</code>, the Parrot Debugger. See <em>docs/debugger.pod</em> for details on it.</p>
+247c247
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/byteorder.pod.html parrot/docs/html/docs/dev/byteorder.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Byteorder Conversion Functions
+---
+>                     Byteorder Conversion Functions
+54c54
+< <p>When reading a pbc stored in a different architecture, the pbc header defines the pbc byteorder for the architecture which stored the pbc, and the <em><a href="../../src/packfile/pf_items.c.html">src/packfile/pf_items.c</a></em> functions are used to convert the values to the native endianness, wordsize and ptrsize.</p>
+---
+> <p>When reading a pbc stored in a different architecture, the pbc header defines the pbc byteorder for the architecture which stored the pbc, and the <em>src/packfile/pf_items.c</em> functions are used to convert the values to the native endianness, wordsize and ptrsize.</p>
+129c129
+< <p>The fetch and transformer functions are implemented in <em><a href="../../src/packfile/pf_items.c.html">src/packfile/pf_items.c</a></em></p>
+---
+> <p>The fetch and transformer functions are implemented in <em>src/packfile/pf_items.c</em></p>
+133c133
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/c_functions.pod.html parrot/docs/html/docs/dev/c_functions.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; C function decoration guidelines
+---
+>                     C function decoration guidelines
+214c214
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/debugging_with_msvc.pod.html parrot/docs/html/docs/dev/debugging_with_msvc.pod.html
 5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Getting Started</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Getting Started
-154c154
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pct/ch03_compiler_tools.pod.html parrot-trunk/docs/html/docs/book/pct/ch03_compiler_tools.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Compiler Tools</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Parrot Compiler Tools
+<         <title>Parrot  - Debugging Parrot with Microsoft</title>
+---
+>         <title>Parrot  - Debugging Parrot with Microsoft Visual C++</title>
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Debugging Parrot with Microsoft
+---
+>                     Debugging Parrot with Microsoft Visual C++
+161c161
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/events.pod.html parrot/docs/html/docs/dev/events.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Design Notes for Events
+---
+>                     Design Notes for Events
+152c152
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/headerizer.pod.html parrot/docs/html/docs/dev/headerizer.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; The Headerizer
+---
+>                     The Headerizer
+26,27c26,27
+< <h1><a name="TITLE"
+< >TITLE</a></h1>
+---
+> <h1><a name="NAME"
+> >NAME</a></h1>
+39c39
+< <p>The Headerizer (<em><a href="../../tools/build/headerizer.pl.html">tools/build/headerizer.pl</a></em>) is a tool that generates chunks of <em>.h</em> header files based on C source code.</p>
+---
+> <p>The Headerizer (<em>tools/build/headerizer.pl</em>) is a tool that generates chunks of <em>.h</em> header files based on C source code.</p>
+66c66
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/infant.pod.html parrot/docs/html/docs/dev/infant.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Infant Mortality
+---
+>                     Infant Mortality
+298c298
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/longopt.pod.html parrot/docs/html/docs/dev/longopt.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Long option parsing
+---
+>                     Long option parsing
+98c98
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/optimizer.pod.html parrot/docs/html/docs/dev/optimizer.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; About the IMCC optimizer
+---
+>                     About the IMCC optimizer
+165c165
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/parrot_api.pod.html parrot/docs/html/docs/dev/parrot_api.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Notes on the PARROT_EXPORT macro
+---
+>                     Notes on the PARROT_EXPORT macro
+64c64
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/pccmethods.pod.html parrot/docs/html/docs/dev/pccmethods.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Parrot Calling Conventions in C
+---
+>                     Parrot Calling Conventions in C
+115c115
+< <p>That is, a register type, followed by a name, optionally followed by one or more flags specified as adverbs. The list of supported adverbs is listed in <em><a href="../pdds/pdd03_calling_conventions.pod.html">docs/pdds/pdd03_calling_conventions.pod</a></em>, the calling conventions design document.</p>
+---
+> <p>That is, a register type, followed by a name, optionally followed by one or more flags specified as adverbs. The list of supported adverbs is listed in <em>docs/pdds/pdd03_calling_conventions.pod</em>, the calling conventions design document.</p>
+141c141
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/pcc_state.pod.html parrot/docs/html/docs/dev/pcc_state.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; parrot calling conventions state table
+---
+>                     parrot calling conventions state table
+134c134
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/pmc_freeze.pod.html parrot/docs/html/docs/dev/pmc_freeze.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Freeze/Thaw Design Notes
+---
+>                     Freeze/Thaw Design Notes
+215c215
+< <p><em><a href="../../src/pmc_freeze.c.html">src/pmc_freeze.c</a></em>, <em>pf/pf_items.c</em></p>
+---
+> <p><em>src/pmc_freeze.c</em>, <em>pf/pf_items.c</em></p>
+224c224
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/pmc_obj_design_meeting_notes.pod.html parrot/docs/html/docs/dev/pmc_obj_design_meeting_notes.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Parrot PMC/Object Design Meeting Notes
+---
+>                     Parrot PMC/Object Design Meeting Notes
+190c190
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/dev/profiling.pod.html parrot/docs/html/docs/dev/profiling.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Name
+---
+>                     Name
+91c91
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/embed.pod.html parrot/docs/html/docs/embed.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Parrot embedding system
+---
+>                     Parrot embedding system
+2224c2224
+< <p><em><a href="../src/main.c.html">src/main.c</a></em> and <em>t/src/*.t</em> for Parrot&#39;s use of the embedding system.</p>
+---
+> <p><em>src/main.c</em> and <em>t/src/*.t</em> for Parrot&#39;s use of the embedding system.</p>
+2230c2230
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/gettingstarted.pod.html parrot/docs/html/docs/gettingstarted.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Parrot Developer FAQ
+---
+>                     Parrot Developer FAQ
+97c97
+< <p>There are a few categories of documentation, each with different intents. It&#39;ll probably help to be aware of them before you go digging in. I highly suggest you check out <em><a href="pdds/pdd07_codingstd.pod.html">/docs/pdds/pdd07_codingstd.pod</a></em> for guidelines on how documentation is supposed to be laid out. For now, here&#39;s the executive summary:</p>
+---
+> <p>There are a few categories of documentation, each with different intents. It&#39;ll probably help to be aware of them before you go digging in. I highly suggest you check out <em>/docs/pdds/pdd07_codingstd.pod</em> for guidelines on how documentation is supposed to be laid out. For now, here&#39;s the executive summary:</p>
+170c170
+< <p>See <em><a href="submissions.pod.html">docs/submissions.pod</a></em> for details.</p>
+---
+> <p>See <em>docs/submissions.pod</em> for details.</p>
+175c175
+< <p>See <em><a href="submissions.pod.html">docs/submissions.pod</a></em> for details.</p>
+---
+> <p>See <em>docs/submissions.pod</em> for details.</p>
+184c184
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/glossary.pod.html parrot/docs/html/docs/glossary.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Parrot Glossary
+---
+>                     Parrot Glossary
+206c206
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/intro.pod.html parrot/docs/html/docs/intro.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; The Parrot Primer
+---
+>                     The Parrot Primer
+181c181
+< <p>The first step to building Parrot is to run the <em><a href="../Configure.pl.html">Configure.pl</a></em> program,
+---
+> <p>The first step to building Parrot is to run the <em>Configure.pl</em> program,
+399c399
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/memory_internals.pod.html parrot/docs/html/docs/memory_internals.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Memory Internals
+---
+>                     Memory Internals
+72c72
+< <p>See <em><a href="pdds/pdd09_gc.pod.html">docs/pdds/pdd09_gc.pod</a></em> for details about the garbage collector system.</p>
+---
+> <p>See <em>docs/pdds/pdd09_gc.pod</em> for details about the garbage collector system.</p>
+160c160
+< <p>The <em><a href="../Configure.pl.html">Configure.pl</a></em> option <code>&#45;&#45;gc</code> allows one to use either method.</p>
+---
+> <p>The <em>Configure.pl</em> option <code>&#45;&#45;gc</code> allows one to use either method.</p>
+221c221
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+Only in parrot-trunk/docs/html/docs: ops
+diff -r parrot-trunk/docs/html/docs/overview.pod.html parrot/docs/html/docs/overview.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; A Parrot Overview
+---
+>                     A Parrot Overview
+159c159
+< <p>One interesting thing about vtables is that you can construct them dynamically. You can find out more about vtables in <em><a href="vtables.pod.html">docs/vtables.pod</a></em>.</p>
+---
+> <p>One interesting thing about vtables is that you can construct them dynamically. You can find out more about vtables in <em>docs/vtables.pod</em>.</p>
+181c181
+< <p>The bytecode format is fully documented in <em><a href="parrotbyte.pod.html">docs/parrotbyte.pod</a></em>.</p>
+---
+> <p>The bytecode format is fully documented in <em>docs/parrotbyte.pod</em>.</p>
+185c185
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+Only in parrot-trunk/docs/html/docs: packfile-c.pod.html
+diff -r parrot-trunk/docs/html/docs/parrotbyte.pod.html parrot/docs/html/docs/parrotbyte.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; The Parrot Bytecode (PBC) Format
+---
+>                     The Parrot Bytecode (PBC) Format
+48c48
+< <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32&#45;bit) or 8 (64 bit). The bytecode loader is responsible for transforming the file into the VM native wordsize on the fly. For performance, a utility <em>pbc_dump</em> is provided to convert PBCs on disk if they cannot be recompiled. See <em><a href="../src/pbc_dump.c.html">src/pbc_dump.c</a></em> for more information.</p>
+---
+> <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32&#45;bit) or 8 (64 bit). The bytecode loader is responsible for transforming the file into the VM native wordsize on the fly. For performance, a utility <em>pbc_dump</em> is provided to convert PBCs on disk if they cannot be recompiled. See <em>src/pbc_dump.c</em> for more information.</p>
+319c319
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/parrothist.pod.html parrot/docs/html/docs/parrothist.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Parrot Release History
+---
+>                     Parrot Release History
+29c29
+< <p>parrothist &#45; Parrot Release History</p>
+---
+> <p>docs/parrothist.pod &#45; Parrot Release History</p>
+158c158
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/parrot.pod.html parrot/docs/html/docs/parrot.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Parrot
+---
+>                     Parrot
+128c128
+< The list is archived at: <a href='http://groups.google.com/group/parrot&#45;dev/'><a href="http://groups.google.com/group/parrot&#45;dev/">http://groups.google.com/group/parrot&#45;dev/</a></a> Many people have contributed their time and expertise to the Parrot project; see the <em><a href="../CREDITS.html">CREDITS</a></em> file for details.</p>
+---
+> The list is archived at: <a href='http://groups.google.com/group/parrot&#45;dev/'><a href="http://groups.google.com/group/parrot&#45;dev/">http://groups.google.com/group/parrot&#45;dev/</a></a> Many people have contributed their time and expertise to the Parrot project; see the <em>CREDITS</em> file for details.</p>
+147c147
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+Only in parrot-trunk/docs/html/docs: pct
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd01_overview.pod.html parrot/docs/html/docs/pdds/draft/pdd01_overview.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 1: Overview
+---
+>                     [DRAFT] PDD 1: Overview
+306c306
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html parrot/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 5: Opcodes
+---
+>                     [DRAFT] PDD 5: Opcodes
+189c189
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd06_pasm.pod.html parrot/docs/html/docs/pdds/draft/pdd06_pasm.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 6: Parrot Assembly Language (PASM)
+---
+>                     [DRAFT] PDD 6: Parrot Assembly Language (PASM)
+168c168
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd08_keys.pod.html parrot/docs/html/docs/pdds/draft/pdd08_keys.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 8: PMC Keys
+---
+>                     [DRAFT] PDD 8: PMC Keys
+214c214
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd10_embedding.pod.html parrot/docs/html/docs/pdds/draft/pdd10_embedding.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD10: Embedding and Extending
+---
+>                     [DRAFT] PDD10: Embedding and Extending
+260c260
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd11_extending.pod.html parrot/docs/html/docs/pdds/draft/pdd11_extending.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 11: Extending
+---
+>                     [DRAFT] PDD 11: Extending
+40c40
+< <p>$Revision: 47669 $</p>
+---
+> <p>$Revision: 48025 $</p>
+326c326
+< <p><em><a href="../../glossary.pod.html">docs/glossary.pod</a></em></p>
+---
+> <p><em>docs/glossary.pod</em></p>
+330c330
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd14_numbers.pod.html parrot/docs/html/docs/pdds/draft/pdd14_numbers.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 14: Numbers
+---
+>                     [DRAFT] PDD 14: Numbers
+489c489
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd16_native_call.pod.html parrot/docs/html/docs/pdds/draft/pdd16_native_call.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 16: Native Call Interface (NCI)
+---
+>                     [DRAFT] PDD 16: Native Call Interface (NCI)
+319c319
+< <p><em><a href="../../../t/pmc/nci.t.html">t/pmc/nci.t</a></em>, <em><a href="../../../src/nci_test.c.html">src/nci_test.c</a></em></p>
+---
+> <p><em>t/pmc/nci.t</em>, <em>src/nci_test.c</em></p>
+323c323
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd29_compiler_tools.pod.html parrot/docs/html/docs/pdds/draft/pdd29_compiler_tools.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 29: Compiler Tools
+---
+>                     [DRAFT] PDD 29: Compiler Tools
+339c339
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd31_hll_interop.pod.html parrot/docs/html/docs/pdds/draft/pdd31_hll_interop.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 31: Inter&#45;Language Calling
+---
+>                     [DRAFT] PDD 31: Inter&#45;Language Calling
+373c373
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd31_hll.pod.html parrot/docs/html/docs/pdds/draft/pdd31_hll.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 31: HLL Compilers and Libraries
+---
+>                     [DRAFT] PDD 31: HLL Compilers and Libraries
+192c192
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd00_pdd.pod.html parrot/docs/html/docs/pdds/pdd00_pdd.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 0: Design Document Format
+---
+>                     PDD 0: Design Document Format
+92c92
+< An example of the currently accepted layout is given in <em><a href="pdd_template.pod.html">docs/pdds/pdd_template.pod</a></em>,
+---
+> An example of the currently accepted layout is given in <em>docs/pdds/pdd_template.pod</em>,
+177c177
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd03_calling_conventions.pod.html parrot/docs/html/docs/pdds/pdd03_calling_conventions.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 3: Calling Conventions
+---
+>                     PDD 3: Calling Conventions
+299c299
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd07_codingstd.pod.html parrot/docs/html/docs/pdds/pdd07_codingstd.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 7: Conventions and Guidelines for Parrot Source Code
+---
+>                     PDD 7: Conventions and Guidelines for Parrot Source Code
+32c32
+< <p>$Revision: 45652 $</p>
+---
+> <p>$Revision: 47658 $</p>
+410c410
+< <p>The <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em> test checks that the files needing this property have it set.</p>
+---
+> <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
+423c423
+< <p>The <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em> test checks that the files needing this property have it set.</p>
+---
+> <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
+428c428
+< <p>The <code>svn:eol&#45;style</code> property makes sure that whenever a file is checked out of subversion it has the correct end&#45;of&#45;line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol&#45;style</code> property set to <code>native</code>. However, this is not true for all files. Some input files to tests (such as the <code>*.input</code> and <code>*.output</code> files for PIR tests) need to have <code>LF</code> as their <code>svn:eol&#45;style</code> property. The current list of such files is described in <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em>.</p>
+---
+> <p>The <code>svn:eol&#45;style</code> property makes sure that whenever a file is checked out of subversion it has the correct end&#45;of&#45;line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol&#45;style</code> property set to <code>native</code>. However, this is not true for all files. Some input files to tests (such as the <code>*.input</code> and <code>*.output</code> files for PIR tests) need to have <code>LF</code> as their <code>svn:eol&#45;style</code> property. The current list of such files is described in <em>t/distro/file_metadata.t</em>.</p>
+438c438
+< <p>The <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em> test checks that the files needing this property have it set.</p>
+---
+> <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
+567,569c567,569
+< This inline Pod documentation is parsed to HTML by running:
+< <pre>    $ perl tools/docs/write_docs.pl &#45;&#45;delete</pre>
+< or: $ make html
+---
+> This inline Pod documentation is transformed to HTML with:
+> <pre>    $ make html</pre>
+> 
+640c640
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd09_gc.pod.html parrot/docs/html/docs/pdds/pdd09_gc.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 9: Garbage Collection Subsystem
+---
+>                     PDD 9: Garbage Collection Subsystem
+680c680
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd13_bytecode.pod.html parrot/docs/html/docs/pdds/pdd13_bytecode.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 13: Bytecode
+---
+>                     PDD 13: Bytecode
+990c990
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd15_objects.pod.html parrot/docs/html/docs/pdds/pdd15_objects.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 15: Objects and Classes
+---
+>                     PDD 15: Objects and Classes
+1273c1273
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd17_pmc.pod.html parrot/docs/html/docs/pdds/pdd17_pmc.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 17: Polymorphic Containers
+---
+>                     PDD 17: Polymorphic Containers
+91c91
+< <p><code>_metadata</code> holds internal PMC metadata (properties). See the setprop/getprop ops in <em><a href="../ops/pmc.pod.html">docs/ops/pmc.pod</a></em>.</p>
+---
+> <p><code>_metadata</code> holds internal PMC metadata (properties). See the setprop/getprop ops in <em>docs/ops/pmc.pod</em>.</p>
+797c797
+< Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating&#45;point number and store the remainder in <i>dest</i>. Note that <i>dest</i> may be the same PMC as <i>self</i>; in that case optimizations may be made. The <code>i_</code> variants perform an inplace operation, modifying the value of <i>self</i>.Note that <code>modulus</code> uses Knuth&#39;s &#34;corrected mod&#34; algorithm, as implemented in <em><a href="../../src/utils.c.html">src/utils.c</a></em>, while <code>cmodulus</code> uses the C&#45;style fmod function.
+---
+> Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating&#45;point number and store the remainder in <i>dest</i>. Note that <i>dest</i> may be the same PMC as <i>self</i>; in that case optimizations may be made. The <code>i_</code> variants perform an inplace operation, modifying the value of <i>self</i>.Note that <code>modulus</code> uses Knuth&#39;s &#34;corrected mod&#34; algorithm, as implemented in <em>src/utils.c</em>, while <code>cmodulus</code> uses the C&#45;style fmod function.
+1228c1228
+< <p><em><a href="../pmc2c.pod.html">docs/pmc2c.pod</a></em></p>
+---
+> <p><em>docs/pmc2c.pod</em></p>
+1232c1232
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd18_security.pod.html parrot/docs/html/docs/pdds/pdd18_security.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 18: Security Model
+---
+>                     PDD 18: Security Model
+234c234
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd19_pir.pod.html parrot/docs/html/docs/pdds/pdd19_pir.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 19: Parrot Intermediate Representation (PIR)
+---
+>                     PDD 19: Parrot Intermediate Representation (PIR)
+838c838
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd20_lexical_vars.pod.html parrot/docs/html/docs/pdds/pdd20_lexical_vars.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 20: Lexical Variables
+---
+>                     PDD 20: Lexical Variables
+312c312
+< <p><em><a href="../../t/op/lexicals.t.html">t/op/lexicals.t</a></em></p>
+---
+> <p><em>t/op/lexicals.t</em></p>
+316c316
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd21_namespaces.pod.html parrot/docs/html/docs/pdds/pdd21_namespaces.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 21: Namespaces
+---
+>                     PDD 21: Namespaces
+436c436
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd22_io.pod.html parrot/docs/html/docs/pdds/pdd22_io.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 22: I/O
+---
+>                     PDD 22: I/O
+755c755
+< <p><em><a href="../../src/io/core.c.html">src/io/core.c</a></em>, <em><a href="../../src/ops/io.ops.html">src/ops/io.ops</a></em>, <em>include/parrot/io.h</em>, <em>runtime/parrot/library/Stream/*</em>, <em><a href="../../src/io/unix.c.html">src/io/unix.c</a></em>, <em><a href="../../src/io/win32.c.html">src/io/win32.c</a></em>, Perl 5&#39;s IO::AIO, and POE</p>
+---
+> <p><em>src/io/core.c</em>, <em>src/ops/io.ops</em>, <em>include/parrot/io.h</em>, <em>runtime/parrot/library/Stream/*</em>, <em>src/io/unix.c</em>, <em>src/io/win32.c</em>, Perl 5&#39;s IO::AIO, and POE</p>
+759c759
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd23_exceptions.pod.html parrot/docs/html/docs/pdds/pdd23_exceptions.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 23: Exceptions
+---
+>                     PDD 23: Exceptions
+425,428c425,428
+< <p><em><a href="../../src/ops/core.ops.html">src/ops/core.ops</a></em>,
+< <em><a href="../../src/exceptions.c.html">src/exceptions.c</a></em>,
+< <em><a href="../../src/pmc/exception.pmc.html">src/pmc/exception.pmc</a></em>,
+< <em><a href="../../src/pmc/exceptionhandler.pmc.html">src/pmc/exceptionhandler.pmc</a></em></p>
+---
+> <p><em>src/ops/core.ops</em>,
+> <em>src/exceptions.c</em>,
+> <em>src/pmc/exception.pmc</em>,
+> <em>src/pmc/exceptionhandler.pmc</em></p>
+432c432
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd24_events.pod.html parrot/docs/html/docs/pdds/pdd24_events.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 24: Events
+---
+>                     PDD 24: Events
+336c336
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd25_concurrency.pod.html parrot/docs/html/docs/pdds/pdd25_concurrency.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 25: Concurrency
+---
+>                     PDD 25: Concurrency
+231c231
+< and a set of core routines in <em><a href="../../src/scheduler.c.html">src/scheduler.c</a></em>.</p>
+---
+> and a set of core routines in <em>src/scheduler.c</em>.</p>
+437c437
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd26_ast.pod.html parrot/docs/html/docs/pdds/pdd26_ast.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 26: Compiler Tools &#45; Abstract Syntax Tree
+---
+>                     PDD 26: Compiler Tools &#45; Abstract Syntax Tree
+374c374
+< The table of PIR opcodes that PAST &#34;knows&#34; about is given in <em><a href="../../compilers/pct/src/PAST/Compiler.pir.html">compilers/pct/src/PAST/Compiler.pir</a></em> .
+---
+> The table of PIR opcodes that PAST &#34;knows&#34; about is given in <em>compilers/pct/src/PAST/Compiler.pir</em> .
+456c456
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd27_multiple_dispatch.pod.html parrot/docs/html/docs/pdds/pdd27_multiple_dispatch.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 27: Multiple Dispatch
+---
+>                     PDD 27: Multiple Dispatch
+262c262
+< <p><em>docs/mmd.pod</em>, <em><a href="../../src/multidispatch.c.html">src/multidispatch.c</a></em>, <em><a href="../../src/pmc/multisub.pmc.html">src/pmc/multisub.pmc</a></em></p>
+---
+> <p><em>docs/mmd.pod</em>, <em>src/multidispatch.c</em>, <em>src/pmc/multisub.pmc</em></p>
+266c266
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd28_strings.pod.html parrot/docs/html/docs/pdds/pdd28_strings.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 28: Strings
+---
+>                     PDD 28: Strings
+739c739
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd30_install.pod.html parrot/docs/html/docs/pdds/pdd30_install.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 30: Installation
+---
+>                     PDD 30: Installation
+41c41
+< <p>$Revision: 47917 $</p>
+---
+> <p>$Revision: 48025 $</p>
+120c120
+< <p>A new language is generated by <em><a href="../../tools/dev/mk_language_shell.pl.html">tools/dev/mk_language_shell.pl</a></em></p>
+---
+> <p>A new language is generated by <em>tools/dev/mk_language_shell.pl</em></p>
+122c122
+< <p>The makefiles are generated from a makefile template, which can use conditional platform and config logic. The forward slashes are automatically converted to backslashes for MSWin32 and <code>\n</code> is converted to <code>\r\n</code> for MSWin32 nmake. See <a href='..%2F..%2Flib%2FParrot%2FConfigure%2FCompiler.pm.html'>Parrot::Configure::Compiler</a>.</p>
+---
+> <p>The makefiles are generated from a makefile template, which can use conditional platform and config logic. The forward slashes are automatically converted to backslashes for MSWin32 and <code>\n</code> is converted to <code>\r\n</code> for MSWin32 nmake. See <a href='TODO'>Parrot::Configure::Compiler</a>.</p>
+136c136
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pdds/pdd_template.pod.html parrot/docs/html/docs/pdds/pdd_template.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; Design Document Template
+---
+>                     Design Document Template
+85c85
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pmc/array.pod.html parrot/docs/html/docs/pmc/array.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Array base class
+---
+>                     Array base class
+26,27c26,27
+< <h1><a name="TITLE"
+< >TITLE</a></h1>
+---
+> <h1><a name="NAME"
+> >NAME</a></h1>
+135c135
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+Only in parrot-trunk/docs/html/docs/pmc: documentation.pod.html
+diff -r parrot-trunk/docs/html/docs/pmc/struct.pod.html parrot/docs/html/docs/pmc/struct.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Accessing C Structs from Parrot
+---
+>                     Accessing C Structs from Parrot
+29c29
+< <p>Structures &#45; Accessing C Structs from Parrot</p>
+---
+> <p>Accessing C Structs from Parrot</p>
+286c286
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/pmc/subs.pod.html parrot/docs/html/docs/pmc/subs.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Parrot Subroutines
+---
+>                     Parrot Subroutines
+29c29
+< <p>Subs &#45; Parrot Subroutines</p>
+---
+> <p>Parrot Subroutines</p>
+46c46
+< <p>Parrot comes with different subroutine and related classes which implement CPS (Continuation Passing Style) and PCC (Parrot Calling Conventions) <em><a href="../pdds/pdd03_calling_conventions.pod.html">docs/pdds/pdd03_calling_conventions.pod</a></em>.</p>
+---
+> <p>Parrot comes with different subroutine and related classes which implement CPS (Continuation Passing Style) and PCC (Parrot Calling Conventions) <em>docs/pdds/pdd03_calling_conventions.pod</em>.</p>
+328c328
+< <p><em><a href="../../src/pmc/sub.pmc.html">src/pmc/sub.pmc</a></em>, <em>src/pmc/closure.pmc</em>, <em><a href="../../src/pmc/continuation.pmc.html">src/pmc/continuation.pmc</a></em>, <em><a href="../../src/pmc/coroutine.pmc.html">src/pmc/coroutine.pmc</a></em>, <em><a href="../../src/sub.c.html">src/sub.c</a></em>, <em><a href="../../t/pmc/sub.t.html">t/pmc/sub.t</a></em></p>
+---
+> <p><em>src/pmc/sub.pmc</em>, <em>src/pmc/closure.pmc</em>, <em>src/pmc/continuation.pmc</em>, <em>src/pmc/coroutine.pmc</em>, <em>src/sub.c</em>, <em>t/pmc/sub.t</em></p>
+333c333
+< <p><em><a href="../pdds/pdd03_calling_conventions.pod.html">docs/pdds/pdd03_calling_conventions.pod</a></em> <em><a href="../pdds/pdd19_pir.pod.html">docs/pdds/pdd19_pir.pod</a></em></p>
+---
+> <p><em>docs/pdds/pdd03_calling_conventions.pod</em> <em>docs/pdds/pdd19_pir.pod</em></p>
 342c342
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pct/ch04_pge.pod.html parrot-trunk/docs/html/docs/book/pct/ch04_pge.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Grammar Engine</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Grammar Engine
-631c631
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pct/ch05_nqp.pod.html parrot-trunk/docs/html/docs/book/pct/ch05_nqp.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Grammar Actions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Grammar Actions
-226c226
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch01_introduction.pod.html parrot-trunk/docs/html/docs/book/pir/ch01_introduction.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Introduction</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Introduction
-162c162
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch02_getting_started.pod.html parrot-trunk/docs/html/docs/book/pir/ch02_getting_started.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Getting Started</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Getting Started
-60c60
-< <p>To install Parrot in a different location, use the <code>&#45;&#45;prefix</code> option to <em>Configure.pl</em>:</p>
----
-> <p>To install Parrot in a different location, use the <code>&#45;&#45;prefix</code> option to <em><a href="../../../Configure.pl.html">Configure.pl</a></em>:</p>
-87c87
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch03_basic_syntax.pod.html parrot-trunk/docs/html/docs/book/pir/ch03_basic_syntax.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Basic Syntax</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Basic Syntax
-216c216
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch04_variables.pod.html parrot-trunk/docs/html/docs/book/pir/ch04_variables.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Variables</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Variables
-279,284c279,291
-< Both C<and> and C<or> are short-circuiting ops. If they can determine what
-< value to return from the first argument, they'll never evaluate the second.
-< This is significant only for PMCs, as they might have side effects on
-< evaluation.The C<xor>X<xor opcode> opcode returns the first argument if it is the only
-< true value, returns the second argument if it is the only true value, and
-< returns false if both values are true or both are false:<pre>  $I0 = xor 1, 0  # returns 1
----
-> </pre>
-> <p>Both <code>and</code> and <code>or</code> are short&#45;circuiting ops.
-> If they can determine what value to return from the first argument,
-> they&#39;ll never evaluate the second.
-> This is significant only for PMCs,
-> as they might have side effects on evaluation.</p>
-> 
-> <p>The <code>xor</code><!--
->       INDEX: xor opcode
-> --> opcode returns the first argument if it is the only true value,
-> returns the second argument if it is the only true value,
-> and returns false if both values are true or both are false:</p>
-> <pre>  $I0 = xor 1, 0  # returns 1
-289,290c296,298
-< The C<not>X<not opcode> opcode returns a true value when the argument is false
-< and a false value if the argument is true:
----
-> <p>The <code>not</code><!--
->       INDEX: not opcode
-> --> opcode returns a true value when the argument is false and a false value if the argument is true:</p>
-294,298c302,316
-< X<bitwise opcodes>
-< The bitwise opcodes operate on their values a single bit at a time.
-< C<band>X<band opcode>, C<bor>X<bor opcode>, and C<bxor>X<bxor opcode> return a
-< value that is the logical AND, OR, or XOR of each bit in the source arguments.
-< They each take two arguments.
----
-> <p><!--
->       INDEX: bitwise opcodes
-> --> The bitwise opcodes operate on their values a single bit at a time.
-> <code>band</code><!--
->       INDEX: band opcode
-> -->,
-> <code>bor</code><!--
->       INDEX: bor opcode
-> -->,
-> and <code>bxor</code><!--
->       INDEX: bxor opcode
-> --> return a value that is the logical AND,
-> OR,
-> or XOR of each bit in the source arguments.
-> They each take two arguments.</p>
-306,307c324,326
-< C<band>, C<bor>, and C<bxor> also have variants that modify the result
-< in place.
----
-> <p><code>band</code>,
-> <code>bor</code>,
-> and <code>bxor</code> also have variants that modify the result in place.</p>
-315c334,336
-< C<bnot>X<bnot opcode> is the logical NOT of each bit in the source argument.
----
-> <p><code>bnot</code><!--
->       INDEX: bnot opcode
-> --> is the logical NOT of each bit in the source argument.</p>
-322,326c343,349
-< X<shl opcode>
-< X<shr opcode>
-< X<lsr opcode>
-< The logical and arithmetic shift operations shift their values by a specified
-< number of bits:
----
-> <p><!--
->       INDEX: shl opcode
-> --> <!--
->       INDEX: shr opcode
-> --> <!--
->       INDEX: lsr opcode
-> --> The logical and arithmetic shift operations shift their values by a specified number of bits:</p>
-338,344c361,372
-< X<strings>
-< Parrot strings are buffers of variable-sized data. The most common use of
-< strings is to store text data. Strings can also hold binary or other
-< non-textual data, though this is rare.N<In general, a custom PMC is more
-< useful.> Parrot strings are flexible and powerful, to handle the complexity of
-< human-readable (and computer-representable) text data.  String operations work
-< with string literals, variables, and constants, and with string-like PMCs.
----
-> <p><!--
->       INDEX: strings
-> --> Parrot strings are buffers of variable&#45;sized data.
-> The most common use of strings is to store text data.
-> Strings can also hold binary or other non&#45;textual data,
-> though this is rare.In general,
-> a custom PMC is more useful. Parrot strings are flexible and powerful,
-> to handle the complexity of human&#45;readable (and computer&#45;representable) text data.
-> String operations work with string literals,
-> variables,
-> and constants,
-> and with string&#45;like PMCs.</p>
-349,353c377,381
-< X<string escapes>
-< X<escape sequences>
-< 
-< Strings in double-quotes allow escape sequences using backslashes. Strings in
-< single-quotes only allow escapes for nested quotes:
----
-> <p><!--
->       INDEX: string escapes
-> --> <!--
->       INDEX: escape sequences
-> --></p>
-355,356c383,384
-<   $S0 = "This string is \n on two lines"
-<   $S0 = 'This is a \n one-line string with a slash in it'
----
-> <p>Strings in double&#45;quotes allow escape sequences using backslashes.
-> Strings in single&#45;quotes only allow escapes for nested quotes:</p>
-357a386,387
-> <pre>  $S0 = &#34;This string is \n on two lines&#34;
->   $S0 = &#39;This is a \n one&#45;line string with a slash in it&#39;</pre>
-359,360c389
-< Table 4.1 shows the escape sequences Parrot supports in double-quoted
-< strings.
----
-> <p>Table 4.1 shows the escape sequences Parrot supports in double&#45;quoted strings.</p>
-365,375c394,396
-< X<heredocs>
-< If you need more flexibility in defining a string, use a heredoc string
-< literal. The C<E<lt>E<lt>> operator starts a heredoc.  The string terminator
-< immediately follows. All text until the terminator is part of the string. The
-< terminator must appear on its own line, must appear at the beginning of the
-< line, and may not have any trailing whitespace.
-< 
-<   $S2 = <<"End_Token"
-<   This is a multi-line string literal. Notice that
-<   it doesn't use quotation marks.
-<   End_Token
----
-> <p><!--
->       INDEX: heredocs
-> --> If you need more flexibility in defining a string, use a heredoc string literal. The <code>&#60;&#60;</code> operator starts a heredoc. The string terminator immediately follows. All text until the terminator is part of the string. The terminator must appear on its own line, must appear at the beginning of the line, and may not have any trailing whitespace.</p>
-376a398,401
-> <pre>  $S2 = &#60;&#60;&#34;End_Token&#34;
->   This is a multi&#45;line string literal. Notice that
->   it doesn&#39;t use quotation marks.
->   End_Token</pre>
-381,382c406,410
-< X<. operator>
-< X<strings;concatenation>
----
-> <p><!--
->       INDEX: . operator
-> --> <!--
->       INDEX: strings;concatenation
-> --></p>
-384,386c412
-< Use the C<.> operator to concatenate strings. The following example
-< concatenates the string "cd" onto the string "ab" and stores the result in
-< C<$S1>.
----
-> <p>Use the <code>.</code> operator to concatenate strings. The following example concatenates the string &#34;cd&#34; onto the string &#34;ab&#34; and stores the result in <code>$S1</code>.</p>
-391,394c417,419
-< X<.= operator>
-< Concatenation has a C<.=> variant to modify the result in place. In the
-< next example, the C<.=> operation appends "xy" onto the string "abcd" in
-< C<$S1>.
----
-> <p><!--
->       INDEX: .= operator
-> --> Concatenation has a <code>.=</code> variant to modify the result in place. In the next example, the <code>.=</code> operation appends &#34;xy&#34; onto the string &#34;abcd&#34; in <code>$S1</code>.</p>
-401,402c426,428
-< X<repeat opcode>
-< The C<repeat> opcode repeats a string a specified number of times:
----
-> <p><!--
->       INDEX: repeat opcode
-> --> The <code>repeat</code> opcode repeats a string a specified number of times:</p>
-407,408c433
-< In this example, C<repeat> generates a new string with "a" repeated five
-< times and stores it in C<$S1>.
----
-> <p>In this example, <code>repeat</code> generates a new string with &#34;a&#34; repeated five times and stores it in <code>$S1</code>.</p>
-413,415c438,440
-< X<length opcode>
-< The C<length> opcode returns the length of a string in characters. This won't
-< be the same as the length in I<bytes> for multibyte encoded strings:
----
-> <p><!--
->       INDEX: length opcode
-> --> The <code>length</code> opcode returns the length of a string in characters. This won&#39;t be the same as the length in <i>bytes</i> for multibyte encoded strings:</p>
-420c445
-< C<length> has no equivalent for PMC strings.
----
-> <p><code>length</code> has no equivalent for PMC strings.</p>
-425,428c450,452
-< The simplest version of the C<substr>X<substr opcode> opcode takes three
-< arguments: a source string, an offset position, and a length. It returns a
-< substring of the original string, starting from the offset position (0 is the
-< first character) and spanning the length:
----
-> <p>The simplest version of the <code>substr</code><!--
->       INDEX: substr opcode
-> --> opcode takes three arguments: a source string, an offset position, and a length. It returns a substring of the original string, starting from the offset position (0 is the first character) and spanning the length:</p>
-431,444c455,457
-< This example extracts a two-character string from "abcde" at a one-character
-< offset from the beginning of the string (starting with the second character).
-< It generates a new string, "bc", in the destination register C<$S0>.
-< 
-< When the offset position is negative, it counts backward from the end of the
-< string. Thus an offset of -1 starts at the last character of the string.
-< 
-< C<substr> no longer has a four-argument form, as in-place string operations
-< have been removed.  There is a C<replace> operator which will perform the
-< replacement and return a new_string without modifying the old_string.
-< The arguments are new_string, old_string, offset, count and
-< replacement_string.  The old_string is copied to the new_string with the
-< replacement_string inserted from offset replacing the content for count
-< characters.
----
-> <p>This example extracts a two&#45;character string from &#34;abcde&#34; at a one&#45;character offset from the beginning of the string (starting with the second character). It generates a new string, &#34;bc&#34;, in the destination register <code>$S0</code>.</p>
-> 
-> <p>When the offset position is negative, it counts backward from the end of the string. Thus an offset of &#45;1 starts at the last character of the string.</p>
-446,447c459,461
-< This example replaces the substring "bc" in C<$S1> with the string "XYZ",
-< and returns "aXYZde" in C<$S0>, C<$S1> is not changed:
----
-> <p><code>substr</code> no longer has a four&#45;argument form, as in&#45;place string operations have been removed. There is a <code>replace</code> operator which will perform the replacement and return a new_string without modifying the old_string. The arguments are new_string, old_string, offset, count and replacement_string. The old_string is copied to the new_string with the replacement_string inserted from offset replacing the content for count characters.</p>
-> 
-> <p>This example replaces the substring &#34;bc&#34; in <code>$S1</code> with the string &#34;XYZ&#34;, and returns &#34;aXYZde&#34; in <code>$S0</code>, <code>$S1</code> is not changed:</p>
-453,456c467
-< When the offset position in a C<replace> is one character beyond the original
-< string length, C<replace> appends the replacement string just like the
-< concatenation operator. If the replacement string is an empty string, the
-< opcode removes the characters from the original string in the new string.
----
-> <p>When the offset position in a <code>replace</code> is one character beyond the original string length, <code>replace</code> appends the replacement string just like the concatenation operator. If the replacement string is an empty string, the opcode removes the characters from the original string in the new string.</p>
-464,469c475,479
-< The C<chr>X<chr opcode> opcode takes an integer value and returns the
-< corresponding character in the ASCII character set as a one-character string.
-< The C<ord>X<ord opcode> opcode takes a single character string and returns the
-< integer value of the character at the first position in the string. The integer
-< value of the character will differ depending on the current encoding of the
-< string:
----
-> <p>The <code>chr</code><!--
->       INDEX: chr opcode
-> --> opcode takes an integer value and returns the corresponding character in the ASCII character set as a one&#45;character string. The <code>ord</code><!--
->       INDEX: ord opcode
-> --> opcode takes a single character string and returns the integer value of the character at the first position in the string. The integer value of the character will differ depending on the current encoding of the string:</p>
-473,475c483
-< C<ord> has a two-argument variant that takes a character offset to select
-< a single character from a multicharacter string. The offset must be within
-< the length of the string:
----
-> <p><code>ord</code> has a two&#45;argument variant that takes a character offset to select a single character from a multicharacter string. The offset must be within the length of the string:</p>
-478,479c486
-< A negative offset counts backward from the end of the string, so -1 is
-< the last character.
----
-> <p>A negative offset counts backward from the end of the string, so &#45;1 is the last character.</p>
-485c492,494
-< X<strings;formatting>
----
-> <p><!--
->       INDEX: strings;formatting
-> --></p>
-487,490c496,498
-< The C<sprintf>X<sprintf opcode> opcode generates a formatted string from a
-< series of values. It takes two arguments: a string specifying the format, and
-< an array PMC containing the values to be formatted. The format string and the
-< result can be either strings or PMCs:
----
-> <p>The <code>sprintf</code><!--
->       INDEX: sprintf opcode
-> --> opcode generates a formatted string from a series of values. It takes two arguments: a string specifying the format, and an array PMC containing the values to be formatted. The format string and the result can be either strings or PMCs:</p>
-494,510c502,508
-< The format string is similar to C's C<sprintf> function with extensions for
-< Parrot data types. Each format field in the string starts with a C<%> and ends
-< with a character specifying the output format. Table 4.2 lists the available
-< output format characters.
-< 
-< Each format field supports several specifier options: R<flags>, R<width>,
-< R<precision>, and R<size>.  Table 4.3 lists the format flags.
-< 
-< The R<width> is a number defining the minimum width of the output from
-< a field. The R<precision> is the maximum width for strings or
-< integers, and the number of decimal places for floating-point fields.
-< If either R<width> or R<precision> is an asterisk (C<*>), it takes its
-< value from the next argument in the PMC.
-< 
-< The R<size> modifier defines the type of the argument the field takes.
-< Table 4.4 lists the size flags. The values in the aggregate PMC must
-< have a type compatible with the specified R<size>.
----
-> <p>The format string is similar to C&#39;s <code>sprintf</code> function with extensions for Parrot data types. Each format field in the string starts with a <code>%</code> and ends with a character specifying the output format. Table 4.2 lists the available output format characters.</p>
-> 
-> <p>Each format field supports several specifier options: flags, width, precision, and size. Table 4.3 lists the format flags.</p>
-> 
-> <p>The width is a number defining the minimum width of the output from a field. The precision is the maximum width for strings or integers, and the number of decimal places for floating&#45;point fields. If either width or precision is an asterisk (<code>*</code>), it takes its value from the next argument in the PMC.</p>
-> 
-> <p>The size modifier defines the type of the argument the field takes. Table 4.4 lists the size flags. The values in the aggregate PMC must have a type compatible with the specified size.</p>
-514,519c512
-< The format string of this C<sprintf> example has two format fields. The first,
-< C<%#Px>, extracts a PMC argument (C<P>) from the aggregate C<$P2> and formats
-< it as a hexadecimal integer (C<x>) with a leading 0x (C<#>). The second format
-< field, C<%+2.3Pf>, takes a PMC argument (C<P>) and formats it as a
-< floating-point number (C<f>) with a minimum of two whole digits and a maximum
-< of three decimal places (C<2.3>) and a leading sign (C<+>).
----
-> <p>The format string of this <code>sprintf</code> example has two format fields. The first, <code>%#Px</code>, extracts a PMC argument (<code>P</code>) from the aggregate <code>$P2</code> and formats it as a hexadecimal integer (<code>x</code>) with a leading 0x (<code>#</code>). The second format field, <code>%+2.3Pf</code>, takes a PMC argument (<code>P</code>) and formats it as a floating&#45;point number (<code>f</code>) with a minimum of two whole digits and a maximum of three decimal places (<code>2.3</code>) and a leading sign (<code>+</code>).</p>
-521,522c514
-< The test files F<t/op/string.t> and F<t/op/sprintf.t> have many more
-< examples of format strings.
----
-> <p>The test files <em><a href="../../../t/op/string.t.html">t/op/string.t</a></em> and <em><a href="../../../t/op/sprintf.t.html">t/op/sprintf.t</a></em> have many more examples of format strings.</p>
-527,529c519,521
-< The C<join>X<join opcode> opcode joins the elements of an array PMC into
-< a single string. The first argument separates the individual elements of
-< the PMC in the final string result.
----
-> <p>The <code>join</code><!--
->       INDEX: join opcode
-> --> opcode joins the elements of an array PMC into a single string. The first argument separates the individual elements of the PMC in the final string result.</p>
-539,541c531
-< This example builds a C<Array> in C<$P0> with the values C<"hi">, C<0>, C<1>,
-< C<0>, and C<"parrot">. It then joins those values (separated by the string
-< C<"__">) into a single string stored in C<$S0>.
----
-> <p>This example builds a <code>Array</code> in <code>$P0</code> with the values <code>&#34;hi&#34;</code>, <code>0</code>, <code>1</code>, <code>0</code>, and <code>&#34;parrot&#34;</code>. It then joins those values (separated by the string <code>&#34;__&#34;</code>) into a single string stored in <code>$S0</code>.</p>
-546,547c536
-< Splitting a string yields a new array containing the resulting substrings of
-< the original string.
----
-> <p>Splitting a string yields a new array containing the resulting substrings of the original string.</p>
-549,551c538
-< This example splits the string "abc" into individual characters and stores them
-< in an array in C<$P0>. It then prints out the first and third elements of the
-< array.
----
-> <p>This example splits the string &#34;abc&#34; into individual characters and stores them in an array in <code>$P0</code>. It then prints out the first and third elements of the array.</p>
-561,564c548,550
-< The C<index>X<index opcode> opcode searches for a substring
-< within a string. If it finds the substring, it returns the position
-< where the substring was found as a character offset from the beginning
-< of the string. If it fails to find the substring, it returns -1:
----
-> <p>The <code>index</code><!--
->       INDEX: index opcode
-> --> opcode searches for a substring within a string. If it finds the substring, it returns the position where the substring was found as a character offset from the beginning of the string. If it fails to find the substring, it returns &#45;1:</p>
-570,571c556
-< C<index> also has a three-argument version, where the final argument
-< defines an offset position for starting the search.
----
-> <p><code>index</code> also has a three&#45;argument version, where the final argument defines an offset position for starting the search.</p>
-575,576c560
-< This example finds the second "eb" in "Beeblebrox" instead of the first,
-< because the search skips the first three characters in the string.
----
-> <p>This example finds the second &#34;eb&#34; in &#34;Beeblebrox&#34; instead of the first, because the search skips the first three characters in the string.</p>
-581,585c565,571
-< The numeric bitwise opcodes also have string variants for AND, OR, and XOR:
-< C<bors>X<bors opcode>, C<bands>X<bands opcode>, and C<bxors>X<bxors opcode>.
-< These take string or string-like PMC arguments and perform the logical
-< operation on each byte of the strings to produce the result string.
-< Remember that in-place string operations are no longer available.
----
-> <p>The numeric bitwise opcodes also have string variants for AND, OR, and XOR: <code>bors</code><!--
->       INDEX: bors opcode
-> -->, <code>bands</code><!--
->       INDEX: bands opcode
-> -->, and <code>bxors</code><!--
->       INDEX: bxors opcode
-> -->. These take string or string&#45;like PMC arguments and perform the logical operation on each byte of the strings to produce the result string. Remember that in&#45;place string operations are no longer available.</p>
-595,596c581
-< The bitwise string opcodes produce meaningful results only when used with
-< simple ASCII strings, because Parrot performs bitwise operations per byte.
----
-> <p>The bitwise string opcodes produce meaningful results only when used with simple ASCII strings, because Parrot performs bitwise operations per byte.</p>
-601,604c586,590
-< Strings use copy-on-write (COW)X<copy-on-write>X<COW (copy-on-write)>
-< optimizations. A call to C<$S1 = $S0> doesn't immediately make a copy of
-< C<$S0>, it only makes both variables point to the same string. Parrot
-< doesn't make a copy of the string until one of two strings is modified.
----
-> <p>Strings use copy&#45;on&#45;write (COW)<!--
->       INDEX: copy&#45;on&#45;write
-> --><!--
->       INDEX: COW (copy&#45;on&#45;write)
-> --> optimizations. A call to <code>$S1 = $S0</code> doesn&#39;t immediately make a copy of <code>$S0</code>, it only makes both variables point to the same string. Parrot doesn&#39;t make a copy of the string until one of two strings is modified.</p>
-611,614c597
-< Modifying one of the two variables causes Parrot to create a new string.  This
-< example preserves the existing value in C<$S0> and assigns the new value to the
-< new string in C<$S1>. The benefit of copy-on-write is avoiding the cost of
-< copying strings until the copies are necessary.
----
-> <p>Modifying one of the two variables causes Parrot to create a new string. This example preserves the existing value in <code>$S0</code> and assigns the new value to the new string in <code>$S1</code>. The benefit of copy&#45;on&#45;write is avoiding the cost of copying strings until the copies are necessary.</p>
-619,637c602,610
-< X<charset>
-< X<ASCII character set>
-< X<encoding>
-< Years ago, strings only needed to support the ASCII character set (or
-< charset), a mapping of 128 bit patterns to symbols and English-language
-< characters. This worked as long as everyone using a computer read and
-< wrote English and only used a small handful of punctuation symbols. In
-< other words, it was woefully insufficient. A modern string system must
-< manage charsets in order to make sense out of all the string data in the
-< world. A modern string system must also handle different encodings --
-< ways to represent various charsets in memory and on disk.
-< 
-< Every string in Parrot has an associated encoding and character set. The default
-< charset is 8-bit ASCII, which is almost universally supported.  Double-quoted
-< string constants can have an optional prefix specifying the string's encoding
-< and charset.N<As you might suspect, single-quoted strings do not support this.>
-< Parrot tracks information about encoding and charset internally, and
-< automatically converts strings when necessary to preserve these
-< characteristics. Strings constants may have prefixes of the form C<encoding:charset:>.
----
-> <p><!--
->       INDEX: charset
-> --> <!--
->       INDEX: ASCII character set
-> --> <!--
->       INDEX: encoding
-> --> Years ago, strings only needed to support the ASCII character set (or charset), a mapping of 128 bit patterns to symbols and English&#45;language characters. This worked as long as everyone using a computer read and wrote English and only used a small handful of punctuation symbols. In other words, it was woefully insufficient. A modern string system must manage charsets in order to make sense out of all the string data in the world. A modern string system must also handle different encodings &#45;&#45; ways to represent various charsets in memory and on disk.</p>
-> 
-> <p>Every string in Parrot has an associated encoding and character set. The default charset is 8&#45;bit ASCII, which is almost universally supported. Double&#45;quoted string constants can have an optional prefix specifying the string&#39;s encoding and charset.As you might suspect, single&#45;quoted strings do not support this. Parrot tracks information about encoding and charset internally, and automatically converts strings when necessary to preserve these characteristics. Strings constants may have prefixes of the form <code>encoding:charset:</code>.</p>
-643,663c616,630
-< X<ISO 8859-1 character set>
-< X<Latin 1 character set>
-< X<UCS-2 encoding>
-< X<UTF-8 encoding>
-< X<UTF-16 encoding>
-< Parrot supports the character sets C<ascii>, C<binary>, C<iso-8859-1>
-< (Latin 1), and C<unicode> and the encodings C<fixed_8>, C<ucs2>,
-< C<utf8>, and C<utf16>.
-< 
-< The C<binary> charset treats the string as a buffer of raw unformatted
-< binary data. It isn't really a string per se, because binary data
-< contains no readable characters. This exists to support libraries which
-< manipulate binary data that doesn't easily fit into any other primitive
-< data type.
-< 
-< When Parrot operates on two strings (as in concatenation or comparison), they
-< must both use the same character set and encoding. Parrot will automatically
-< upgrade one or both of the strings to the next highest compatible format as
-< necessary. ASCII strings will automatically upgrade to UTF-8 strings if needed,
-< and UTF-8 will upgrade to UTF-16.  All of these conversions happen inside
-< Parrot, so the programmer doesn't need to worry about the details.
----
-> <p><!--
->       INDEX: ISO 8859&#45;1 character set
-> --> <!--
->       INDEX: Latin 1 character set
-> --> <!--
->       INDEX: UCS&#45;2 encoding
-> --> <!--
->       INDEX: UTF&#45;8 encoding
-> --> <!--
->       INDEX: UTF&#45;16 encoding
-> --> Parrot supports the character sets <code>ascii</code>, <code>binary</code>, <code>iso&#45;8859&#45;1</code> (Latin 1), and <code>unicode</code> and the encodings <code>fixed_8</code>, <code>ucs2</code>, <code>utf8</code>, and <code>utf16</code>.</p>
-> 
-> <p>The <code>binary</code> charset treats the string as a buffer of raw unformatted binary data. It isn&#39;t really a string per se, because binary data contains no readable characters. This exists to support libraries which manipulate binary data that doesn&#39;t easily fit into any other primitive data type.</p>
-> 
-> <p>When Parrot operates on two strings (as in concatenation or comparison), they must both use the same character set and encoding. Parrot will automatically upgrade one or both of the strings to the next highest compatible format as necessary. ASCII strings will automatically upgrade to UTF&#45;8 strings if needed, and UTF&#45;8 will upgrade to UTF&#45;16. All of these conversions happen inside Parrot, so the programmer doesn&#39;t need to worry about the details.</p>
-668,675c635,639
-< X<Polymorphic Containers (PMCs)>
-< X<PMCs (Polymorphic Containers)>
-< Polymorphic Containers (PMCs) are the basis for complex data types and
-< object-oriented behavior in Parrot. In PIR, any variable that isn't a
-< low-level integer, number, or string is a PMC. PMC variables act much
-< like the low-level variables, but you have to instantiate a new PMC
-< object before you use it. The C<new> opcode creates a new PMC object of
-< the specified type.
----
-> <p><!--
->       INDEX: Polymorphic Containers (PMCs)
-> --> <!--
->       INDEX: PMCs (Polymorphic Containers)
-> --> Polymorphic Containers (PMCs) are the basis for complex data types and object&#45;oriented behavior in Parrot. In PIR, any variable that isn&#39;t a low&#45;level integer, number, or string is a PMC. PMC variables act much like the low&#45;level variables, but you have to instantiate a new PMC object before you use it. The <code>new</code> opcode creates a new PMC object of the specified type.</p>
-680,687c644,648
-< This example creates a C<String> object, stores it in the PMC register
-< variable C<$P0>, assigns it the value "That's a bollard and not a
-< parrot", and prints it.
-< 
-< Every PMC has a type that indicates what data it can store and what
-< behavior it supports. The C<typeof>X<typeof opcode> opcode reports the
-< type of a PMC.  When the result is a string variable, C<typeof> returns
-< the name of the type:
----
-> <p>This example creates a <code>String</code> object, stores it in the PMC register variable <code>$P0</code>, assigns it the value &#34;That&#39;s a bollard and not a parrot&#34;, and prints it.</p>
-> 
-> <p>Every PMC has a type that indicates what data it can store and what behavior it supports. The <code>typeof</code><!--
->       INDEX: typeof opcode
-> --> opcode reports the type of a PMC. When the result is a string variable, <code>typeof</code> returns the name of the type:</p>
-692,693c653
-< When the result is a PMC variable, C<typeof> returns the C<Class> PMC
-< for that object type.
----
-> <p>When the result is a PMC variable, <code>typeof</code> returns the <code>Class</code> PMC for that object type.</p>
-698,707c658,664
-< X<scalar PMCs>
-< X<PMCs (Polymorphic Containers);scalar>
-< In most of the examples shown so far, PMCs duplicate the behavior of integers,
-< numbers, and strings. Parrot provides a set of PMCs for this exact purpose.
-< C<Integer>, C<Float>, and C<String> are thin overlays on Parrot's low-level
-< integers, numbers, and strings.
-< 
-< A previous example showed a string literal assigned to a PMC variable of type
-< C<String>. Direct assignment of a literal to a PMC works for all the low-level
-< types and their PMC equivalents:
----
-> <p><!--
->       INDEX: scalar PMCs
-> --> <!--
->       INDEX: PMCs (Polymorphic Containers);scalar
-> --> In most of the examples shown so far, PMCs duplicate the behavior of integers, numbers, and strings. Parrot provides a set of PMCs for this exact purpose. <code>Integer</code>, <code>Float</code>, and <code>String</code> are thin overlays on Parrot&#39;s low&#45;level integers, numbers, and strings.</p>
-> 
-> <p>A previous example showed a string literal assigned to a PMC variable of type <code>String</code>. Direct assignment of a literal to a PMC works for all the low&#45;level types and their PMC equivalents:</p>
-717c674,676
-< X<boxing>
----
-> <p><!--
->       INDEX: boxing
-> --></p>
-719,722c678
-< You may also assign non-constant low-level integer, number, or string registers
-< directly to a PMC. The PMC handles the conversion from the low-level type to
-< its own internal storage.N<This conversion of a simpler type to a more complex
-< type is "boxing".>
----
-> <p>You may also assign non&#45;constant low&#45;level integer, number, or string registers directly to a PMC. The PMC handles the conversion from the low&#45;level type to its own internal storage.This conversion of a simpler type to a more complex type is &#34;boxing&#34;.</p>
-735,736c691
-< The C<box> opcode is a handy shortcut to create the appropriate PMC
-< object from an integer, number, or string literal or variable.
----
-> <p>The <code>box</code> opcode is a handy shortcut to create the appropriate PMC object from an integer, number, or string literal or variable.</p>
-743,746c698,700
-< X<unboxing>
-< In the reverse situation, when assigning a PMC to an integer, number, or
-< string variable, the PMC also has the ability to convert its value to
-< the low-level type.N<The reverse of "boxing" is "unboxing".>
----
-> <p><!--
->       INDEX: unboxing
-> --> In the reverse situation, when assigning a PMC to an integer, number, or string variable, the PMC also has the ability to convert its value to the low&#45;level type.The reverse of &#34;boxing&#34; is &#34;unboxing&#34;.</p>
-762,768c716,724
-< This example creates C<Integer>X<Integer PMC>, C<Float>X<Float PMC>,
-< and C<String>X<String PMC> PMCs, and shows the effect of assigning each
-< one back to a low-level type.
-< 
-< Converting a string to an integer or number only makes sense when the contents
-< of the string are a number. The C<String> PMC will attempt to extract a number
-< from the beginning of the string, but otherwise will return a false value.
----
-> <p>This example creates <code>Integer</code><!--
->       INDEX: Integer PMC
-> -->, <code>Float</code><!--
->       INDEX: Float PMC
-> -->, and <code>String</code><!--
->       INDEX: String PMC
-> --> PMCs, and shows the effect of assigning each one back to a low&#45;level type.</p>
-> 
-> <p>Converting a string to an integer or number only makes sense when the contents of the string are a number. The <code>String</code> PMC will attempt to extract a number from the beginning of the string, but otherwise will return a false value.</p>
-773,778c729,733
-< X<aggregate PMCs>
-< X<PMCs (Polymorphic Containers);aggregate>
-< PMCs can define complex types that hold multiple values, commonly called
-< aggregates. Two basic aggregate types are ordered arrays and associative
-< arrays. The primary difference between these is that ordered arrays use integer
-< keys for indexes and associative arrays use string keys.
----
-> <p><!--
->       INDEX: aggregate PMCs
-> --> <!--
->       INDEX: PMCs (Polymorphic Containers);aggregate
-> --> PMCs can define complex types that hold multiple values, commonly called aggregates. Two basic aggregate types are ordered arrays and associative arrays. The primary difference between these is that ordered arrays use integer keys for indexes and associative arrays use string keys.</p>
-780,781c735
-< Aggregate PMCs support the use of numeric or string keys.  PIR also offers a
-< extensive set of operations for manipulating aggregate data types.
----
-> <p>Aggregate PMCs support the use of numeric or string keys. PIR also offers a extensive set of operations for manipulating aggregate data types.</p>
-786,809c740,748
-< X<arrays>
-< X<ordered arrays>
-< Parrot provides several ordered array PMCs, differentiated by whether
-< the array should store booleans, integers, numbers, strings, or other
-< PMCs, and whether the array should maintain a fixed size or dynamically
-< resize for the number of elements it stores.
-< 
-< The core array types are C<FixedPMCArray>, C<ResizablePMCArray>,
-< C<FixedIntegerArray>, C<ResizableIntegerArray>, C<FixedFloatArray>,
-< C<ResizableFloatArray>, C<FixedStringArray>, C<ResizableStringArray>,
-< C<FixedBooleanArray>, and C<ResizableBooleanArray>. The array
-< types that start with "Fixed" have a fixed size and do not allow
-< elements to be added outside their allocated size. The "Resizable"
-< variants automatically extend themselves as more elements are
-< added.N<With some additional overhead for checking array bounds and
-< reallocating array memory.> The array types that include "String",
-< "Integer", or "Boolean" in the name use alternate packing methods for
-< greater memory efficiency.
-< 
-< Parrot's core ordered array PMCs all have zero-based integer keys. Extracting
-< or inserting an element into the array uses PIR's standard key syntax, with the
-< key in square brackets after the variable name. An lvalue key sets the value
-< for that key.  An rvalue key extracts the value for that key in the aggregate
-< to use as the argument value:
----
-> <p><!--
->       INDEX: arrays
-> --> <!--
->       INDEX: ordered arrays
-> --> Parrot provides several ordered array PMCs, differentiated by whether the array should store booleans, integers, numbers, strings, or other PMCs, and whether the array should maintain a fixed size or dynamically resize for the number of elements it stores.</p>
-> 
-> <p>The core array types are <code>FixedPMCArray</code>, <code>ResizablePMCArray</code>, <code>FixedIntegerArray</code>, <code>ResizableIntegerArray</code>, <code>FixedFloatArray</code>, <code>ResizableFloatArray</code>, <code>FixedStringArray</code>, <code>ResizableStringArray</code>, <code>FixedBooleanArray</code>, and <code>ResizableBooleanArray</code>. The array types that start with &#34;Fixed&#34; have a fixed size and do not allow elements to be added outside their allocated size. The &#34;Resizable&#34; variants automatically extend themselves as more elements are added.With some additional overhead for checking array bounds and reallocating array memory. The array types that include &#34;String&#34;, &#34;Integer&#34;, or &#34;Boolean&#34; in the name use alternate packing methods for greater memory efficiency.</p>
-> 
-> <p>Parrot&#39;s core ordered array PMCs all have zero&#45;based integer keys. Extracting or inserting an element into the array uses PIR&#39;s standard key syntax, with the key in square brackets after the variable name. An lvalue key sets the value for that key. An rvalue key extracts the value for that key in the aggregate to use as the argument value:</p>
-815,817c754
-< Setting the array to an integer value directly (without a key) sets the number
-< of elements of the array.  Assigning an array directly to an integer retrieves
-< the number of elements of the array.
----
-> <p>Setting the array to an integer value directly (without a key) sets the number of elements of the array. Assigning an array directly to an integer retrieves the number of elements of the array.</p>
-821,822c758
-< This is equivalent to using the C<elements> opcode to retrieve the number of
-< items currently in an array:
----
-> <p>This is equivalent to using the <code>elements</code> opcode to retrieve the number of items currently in an array:</p>
-825,829c761
-< Some other useful instructions for working with ordered arrays are
-< C<push>, C<pop>, C<shift>, and C<unshift>, to add or remove elements.
-< C<push> and C<pop> work on the end of the array, the highest numbered
-< index. C<shift> and C<unshift> work on the start of the array, adding or
-< removing the zeroth element, and renumbering all the following elements.
----
-> <p>Some other useful instructions for working with ordered arrays are <code>push</code>, <code>pop</code>, <code>shift</code>, and <code>unshift</code>, to add or remove elements. <code>push</code> and <code>pop</code> work on the end of the array, the highest numbered index. <code>shift</code> and <code>unshift</code> work on the start of the array, adding or removing the zeroth element, and renumbering all the following elements.</p>
-839,847c771,777
-< X<associative arrays>
-< X<hashes>
-< X<dictionaries>
-< An associative array is an unordered aggregate that uses string keys to
-< identify elements.  You may know them as "hash tables", "hashes", "maps", or
-< "dictionaries". Parrot provides one core associative array PMC, called C<Hash>.
-< String keys work very much like integer keys.  An lvalue key sets the value of
-< an element, and an rvalue key extracts the value of an element. The string in
-< the key must always be in single or double quotes.
----
-> <p><!--
->       INDEX: associative arrays
-> --> <!--
->       INDEX: hashes
-> --> <!--
->       INDEX: dictionaries
-> --> An associative array is an unordered aggregate that uses string keys to identify elements. You may know them as &#34;hash tables&#34;, &#34;hashes&#34;, &#34;maps&#34;, or &#34;dictionaries&#34;. Parrot provides one core associative array PMC, called <code>Hash</code>. String keys work very much like integer keys. An lvalue key sets the value of an element, and an rvalue key extracts the value of an element. The string in the key must always be in single or double quotes.</p>
-852,854c782,784
-< Assigning a C<Hash>X<Hash PMC> PMC (without a key) to an integer result
-< fetches the number of elements in the hash.N<You may not set a C<Hash>
-< PMC directly to an integer value.>
----
-> <p>Assigning a <code>Hash</code><!--
->       INDEX: Hash PMC
-> --> PMC (without a key) to an integer result fetches the number of elements in the hash.You may not set a <code>Hash</code> PMC directly to an integer value.</p>
-857,860c787,789
-< The C<exists>X<exists opcode> opcode tests whether a keyed value exists in an
-< aggregate. It returns 1 if it finds the key in the aggregate and 0 otherwise.
-< It doesn't care if the value itself is true or false, only that an entry exists
-< for that key:
----
-> <p>The <code>exists</code><!--
->       INDEX: exists opcode
-> --> opcode tests whether a keyed value exists in an aggregate. It returns 1 if it finds the key in the aggregate and 0 otherwise. It doesn&#39;t care if the value itself is true or false, only that an entry exists for that key:</p>
-866,867c795,797
-< The C<delete>X<delete opcode> opcode removes an element from an associative
-< array:
----
-> <p>The <code>delete</code><!--
->       INDEX: delete opcode
-> --> opcode removes an element from an associative array:</p>
-873,878c803,807
-< X<iterators>
-< X<PMCs (Polymorphic Containers); iterators>
-< An iterator extracts values from an aggregate PMC one at a time.  Iterators are
-< most useful in loops which perform an action on every element in an aggregate.
-< The C<iter> opcode creates a new iterator from an aggregate PMC. It takes one
-< argument, the PMC over which to iterate:
----
-> <p><!--
->       INDEX: iterators
-> --> <!--
->       INDEX: PMCs (Polymorphic Containers); iterators
-> --> An iterator extracts values from an aggregate PMC one at a time. Iterators are most useful in loops which perform an action on every element in an aggregate. The <code>iter</code> opcode creates a new iterator from an aggregate PMC. It takes one argument, the PMC over which to iterate:</p>
-881c810,812
-< The C<shift>X<shift opcode> opcode extracts the next value from the iterator.
----
-> <p>The <code>shift</code><!--
->       INDEX: shift opcode
-> --> opcode extracts the next value from the iterator.</p>
-884,885c815
-< Evaluating the iterator PMC as a boolean returns whether the iterator has
-< reached the end of the aggregate:
----
-> <p>Evaluating the iterator PMC as a boolean returns whether the iterator has reached the end of the aggregate:</p>
-888,896c818,822
-< Parrot provides predefined constants for working with iterators.
-< C<.ITERATE_FROM_START> and C<.ITERATE_FROM_END> constants select whether an
-< ordered array iterator starts from the beginning or end of the array.  These
-< two constants have no effect on associative array iterators, as their elements
-< are unordered.
-< 
-< Load the iterator constants with the C<.include>X<.include directive>
-< directive to include the file F<iterator.pasm>. To use them, set the
-< iterator PMC to the value of the constant:
----
-> <p>Parrot provides predefined constants for working with iterators. <code>.ITERATE_FROM_START</code> and <code>.ITERATE_FROM_END</code> constants select whether an ordered array iterator starts from the beginning or end of the array. These two constants have no effect on associative array iterators, as their elements are unordered.</p>
-> 
-> <p>Load the iterator constants with the <code>.include</code><!--
->       INDEX: .include directive
-> --> directive to include the file <em>iterator.pasm</em>. To use them, set the iterator PMC to the value of the constant:</p>
-903,906c829
-< With all of those separate pieces in one place, this example loads the iterator
-< constants, creates an ordered array of "a", "b", "c", creates an iterator from
-< that array, and then loops over the iterator using a conditional C<goto> to
-< checks the boolean value of the iterator and another unconditional C<goto>:
----
-> <p>With all of those separate pieces in one place, this example loads the iterator constants, creates an ordered array of &#34;a&#34;, &#34;b&#34;, &#34;c&#34;, creates an iterator from that array, and then loops over the iterator using a conditional <code>goto</code> to checks the boolean value of the iterator and another unconditional <code>goto</code>:</p>
-923,925c846
-< Associative array iterators work similarly to ordered array iterators.  When
-< iterating over associative arrays, the C<shift> opcode extracts keys instead of
-< values. The key looks up the value in the original hash PMC.
----
-> <p>Associative array iterators work similarly to ordered array iterators. When iterating over associative arrays, the <code>shift</code> opcode extracts keys instead of values. The key looks up the value in the original hash PMC.</p>
-941,951c862
-< This example creates an associative array C<$P2> that contains three
-< keys "a", "b", and "c", assigning them the values 10, 20, and 30. It
-< creates an iterator (C<$P1>) from the associative array using the
-< C<iter> opcode, and then starts a loop over the iterator. At the start
-< of each loop, the C<unless> instruction checks whether the iterator has
-< any more elements. If there are no more elements, C<goto> jumps to the
-< end of the loop, marked by the label C<iter_end>. If there are more
-< elements, the C<shift> opcode extracts the next key. Keyed assignment
-< stores the integer value of the element indexed by the key in C<$I9>.
-< After printing the integer value, C<goto> jumps back to the start of the
-< loop, marked by C<iter_loop>.
----
-> <p>This example creates an associative array <code>$P2</code> that contains three keys &#34;a&#34;, &#34;b&#34;, and &#34;c&#34;, assigning them the values 10, 20, and 30. It creates an iterator (<code>$P1</code>) from the associative array using the <code>iter</code> opcode, and then starts a loop over the iterator. At the start of each loop, the <code>unless</code> instruction checks whether the iterator has any more elements. If there are no more elements, <code>goto</code> jumps to the end of the loop, marked by the label <code>iter_end</code>. If there are more elements, the <code>shift</code> opcode extracts the next key. Keyed assignment stores the integer value of the element indexed by the key in <code>$I9</code>. After printing the integer value, <code>goto</code> jumps back to the start of the loop, marked by <code>iter_loop</code>.</p>
-956,962c867,871
-< X<keys>
-< X<multi-level keys>
-< Aggregates can hold any data type, including other aggregates.
-< Accessing elements deep within nested data structures is a common
-< operation, so PIR provides a way to do it in a single instruction.
-< Complex keys specify a series of nested data structures, with each
-< individual key separated by a semicolon.
----
-> <p><!--
->       INDEX: keys
-> --> <!--
->       INDEX: multi&#45;level keys
-> --> Aggregates can hold any data type, including other aggregates. Accessing elements deep within nested data structures is a common operation, so PIR provides a way to do it in a single instruction. Complex keys specify a series of nested data structures, with each individual key separated by a semicolon.</p>
-972,975c881
-< This example builds up a data structure of an associative array
-< containing an ordered array. The complex key C<["answer"; $I1]>
-< retrieves an element of the array within the hash. You can also set a
-< value using a complex key:
----
-> <p>This example builds up a data structure of an associative array containing an ordered array. The complex key <code>[&#34;answer&#34;; $I1]</code> retrieves an element of the array within the hash. You can also set a value using a complex key:</p>
-978,979c884
-< The individual keys are integer or string literals, or variables with
-< integer or string values.
----
-> <p>The individual keys are integer or string literals, or variables with integer or string values.</p>
-984,989c889,891
-< X<PMCs (Polymorphic Containers); copying vs. cloning>
-< PMC registers don't directly store the data for a PMC, they only store a
-< pointer to the structure that stores the data. As a result, the C<=>
-< operator doesn't copy the entire PMC, it only copies the pointer to the
-< PMC data. If you later modify the copy of the variable, it will also
-< modify the original.
----
-> <p><!--
->       INDEX: PMCs (Polymorphic Containers); copying vs. cloning
-> --> PMC registers don&#39;t directly store the data for a PMC, they only store a pointer to the structure that stores the data. As a result, the <code>=</code> operator doesn&#39;t copy the entire PMC, it only copies the pointer to the PMC data. If you later modify the copy of the variable, it will also modify the original.</p>
-997,1000c899
-< In this example, C<$P0> and C<$P1> are both pointers to the same
-< internal data structure.  Setting C<$P1> to the string literal
-< "Zaphod", it overwrites the previous value "Ford". Both C<$P0> and
-< C<$P1> refer to the C<String> PMC "Zaphod".
----
-> <p>In this example, <code>$P0</code> and <code>$P1</code> are both pointers to the same internal data structure. Setting <code>$P1</code> to the string literal &#34;Zaphod&#34;, it overwrites the previous value &#34;Ford&#34;. Both <code>$P0</code> and <code>$P1</code> refer to the <code>String</code> PMC &#34;Zaphod&#34;.</p>
-1002,1003c901,905
-< The C<clone> X<clone opcode> opcode makes a deep copy of a PMC, instead
-< of copying the pointer like C<=>X<= operator> does.
----
-> <p>The <code>clone</code> <!--
->       INDEX: clone opcode
-> --> opcode makes a deep copy of a PMC, instead of copying the pointer like <code>=</code><!--
->       INDEX: = operator
-> --> does.</p>
-1011,1018c913,919
-< This example creates an identical, independent clone of the PMC in
-< C<$P0> and puts it in C<$P1>. Later changes to C<$P0> have no effect on
-< the PMC in C<$P1>.N<With low-level strings, the copies created by
-< C<clone> are copy-on-writeX<copy-on-write> exactly the same as the copy
-< created by C<=>.>
-< 
-< To assign the I<value> of one PMC to another PMC that already exists, use the
-< C<assign>X<assign opcode> opcode:
----
-> <p>This example creates an identical, independent clone of the PMC in <code>$P0</code> and puts it in <code>$P1</code>. Later changes to <code>$P0</code> have no effect on the PMC in <code>$P1</code>.With low&#45;level strings, the copies created by <code>clone</code> are copy&#45;on&#45;write<!--
->       INDEX: copy&#45;on&#45;write
-> --> exactly the same as the copy created by <code>=</code>.</p>
-> 
-> <p>To assign the <i>value</i> of one PMC to another PMC that already exists, use the <code>assign</code><!--
->       INDEX: assign opcode
-> --> opcode:</p>
-1027,1032c928
-< This example creates two C<Integer> PMCs, C<$P1> and C<$P2>, and gives the
-< first one the value 42. It then uses C<assign> to pass the same integer value
-< on to C<$P1>. Though C<$P0> increments, C<$P1> doesn't change. The result for
-< C<assign> must have an existing object of the right type in it, because
-< C<assign> neither creates a new duplicate object (as does C<clone>) or reuses
-< the source object (as does C<=>).
----
-> <p>This example creates two <code>Integer</code> PMCs, <code>$P1</code> and <code>$P2</code>, and gives the first one the value 42. It then uses <code>assign</code> to pass the same integer value on to <code>$P1</code>. Though <code>$P0</code> increments, <code>$P1</code> doesn&#39;t change. The result for <code>assign</code> must have an existing object of the right type in it, because <code>assign</code> neither creates a new duplicate object (as does <code>clone</code>) or reuses the source object (as does <code>=</code>).</p>
-1037,1038c933,937
-< X<properties>
-< X<PMCs (Polymorphic Containers); properties>
----
-> <p><!--
->       INDEX: properties
-> --> <!--
->       INDEX: PMCs (Polymorphic Containers); properties
-> --></p>
-1040,1041c939
-< PMCs can have additional values attached to them as "properties" of the
-< PMC. Most properties hold extra metadata about the PMC.
----
-> <p>PMCs can have additional values attached to them as &#34;properties&#34; of the PMC. Most properties hold extra metadata about the PMC.</p>
-1043,1045c941,943
-< The C<setprop>X<setprop opcode> opcode sets the value of a named property on a
-< PMC. It takes three arguments: the PMC on which to set a property, the name of
-< the property, and a PMC containing the value of the property.
----
-> <p>The <code>setprop</code><!--
->       INDEX: setprop opcode
-> --> opcode sets the value of a named property on a PMC. It takes three arguments: the PMC on which to set a property, the name of the property, and a PMC containing the value of the property.</p>
-1048,1050c946,948
-< The C<getprop>X<getprop opcode> opcode returns the value of a property.  It
-< takes two arguments: the name of the property and the PMC from which to
-< retrieve the property value.
----
-> <p>The <code>getprop</code><!--
->       INDEX: getprop opcode
-> --> opcode returns the value of a property. It takes two arguments: the name of the property and the PMC from which to retrieve the property value.</p>
-1053,1056c951
-< This example creates a C<String> object in C<$P0> and an C<Integer> object with
-< the value 1 in C<$P1>. C<setprop> sets a property named "eric" on the object in
-< C<$P0> and gives the property the value of C<$P1>. C<getprop> retrieves the
-< value of the property "eric" on C<$P0> and stores it in C<$P2>.
----
-> <p>This example creates a <code>String</code> object in <code>$P0</code> and an <code>Integer</code> object with the value 1 in <code>$P1</code>. <code>setprop</code> sets a property named &#34;eric&#34; on the object in <code>$P0</code> and gives the property the value of <code>$P1</code>. <code>getprop</code> retrieves the value of the property &#34;eric&#34; on <code>$P0</code> and stores it in <code>$P2</code>.</p>
-1067,1068c962
-< Parrot stores PMC properties in an associative array where the name of the
-< property is the key.
----
-> <p>Parrot stores PMC properties in an associative array where the name of the property is the key.</p>
-1070c964,966
-< C<delprop>X<delprop opcode> deletes a property from a PMC.
----
-> <p><code>delprop</code><!--
->       INDEX: delprop opcode
-> --> deletes a property from a PMC.</p>
-1073,1074c969,971
-< You can fetch a complete hash of all properties on a PMC with
-< C<prophash>X<prophash opcode>:
----
-> <p>You can fetch a complete hash of all properties on a PMC with <code>prophash</code><!--
->       INDEX: prophash opcode
-> -->:</p>
-1077c974
-< Fetching the value of a non-existent property returns an C<Undef> PMC.
----
-> <p>Fetching the value of a non&#45;existent property returns an <code>Undef</code> PMC.</p>
-1082,1104c979,991
-< X<vtable functions>
-< You may have noticed that a simple operation sometimes has a different effect
-< on different PMCs. Assigning a low-level integer value to a C<Integer> PMC sets
-< its integer value of the PMC, but assigning that same integer to an ordered
-< array sets the size of the array.
-< 
-< Every PMC defines a standard set of low-level operations called vtable
-< functions. When you perform an assignment like:
-< 
-<    $P0 = 5
-< 
-< 
-< ... Parrot calls the C<set_integer_native> vtable function on the PMC referred
-< to by register C<$P0>.
-< 
-< X<polymorphic substitution>
-< Parrot has a fixed set of vtable functions, so that any PMC can stand in for
-< any other PMC; they're polymorphic.N<Hence the name "Polymorphic Container".>
-< Every PMC defines some behavior for every vtable function. The default behavior
-< is to throw an exception reporting that the PMC doesn't implement that vtable
-< function. The full set of vtable functions for a PMC defines the PMC's basic
-< interface, but PMCs may also define methods to extend their behavior beyond the
-< vtable set.
----
-> <p><!--
->       INDEX: vtable functions
-> --> You may have noticed that a simple operation sometimes has a different effect on different PMCs. Assigning a low&#45;level integer value to a <code>Integer</code> PMC sets its integer value of the PMC, but assigning that same integer to an ordered array sets the size of the array.</p>
-> 
-> <p>Every PMC defines a standard set of low&#45;level operations called vtable functions. When you perform an assignment like:</p>
-> 
-> <pre>   $P0 = 5</pre>
-> 
-> <p>... Parrot calls the <code>set_integer_native</code> vtable function on the PMC referred to by register <code>$P0</code>.</p>
-> 
-> <p><!--
->       INDEX: polymorphic substitution
-> --> Parrot has a fixed set of vtable functions, so that any PMC can stand in for any other PMC; they&#39;re polymorphic.Hence the name &#34;Polymorphic Container&#34;. Every PMC defines some behavior for every vtable function. The default behavior is to throw an exception reporting that the PMC doesn&#39;t implement that vtable function. The full set of vtable functions for a PMC defines the PMC&#39;s basic interface, but PMCs may also define methods to extend their behavior beyond the vtable set.</p>
-1109,1120c996,1006
-< X<namespaces>
-< X<global variables>
-< Parrot performs operations on variables stored in small register sets local to
-< each subroutine. For more complex tasks,N<...and for most high-level languages
-< that Parrot supports.> it's also useful to have variables that live beyond the
-< scope of a single subroutine. These variables may be global to the entire
-< program or restricted to a particular library. Parrot stores long-lived
-< variables in a hierarchy of namespaces.
-< 
-< The opcodes C<set_global>X<set_global opcode> and
-< C<get_global>X<get_global opcode> store and fetch a variable in a
-< namespace:
----
-> <p><!--
->       INDEX: namespaces
-> --> <!--
->       INDEX: global variables
-> --> Parrot performs operations on variables stored in small register sets local to each subroutine. For more complex tasks,...and for most high&#45;level languages that Parrot supports. it&#39;s also useful to have variables that live beyond the scope of a single subroutine. These variables may be global to the entire program or restricted to a particular library. Parrot stores long&#45;lived variables in a hierarchy of namespaces.</p>
-> 
-> <p>The opcodes <code>set_global</code><!--
->       INDEX: set_global opcode
-> --> and <code>get_global</code><!--
->       INDEX: get_global opcode
-> --> store and fetch a variable in a namespace:</p>
-1128,1144c1014,1018
-< The first two statements in this example create a C<String> PMC in
-< C<$P0> and assign it a value. In the third statement, C<set_global>
-< stores that PMC as the named global variable C<bee>.  At some later
-< point in the program, C<get_global> retrieves the global variable by
-< name, and stores it in C<$P1> to print.
-< 
-< Namespaces can only store PMC variables.  Parrot boxes all primitive integer,
-< number, or string values into the corresponding PMCs before storing them in a
-< namespace.
-< 
-< The name of every variable stored in a particular namespace must be
-< unique. You can't have store both an C<Integer> PMC and an array PMC
-< both named "bee", stored in the same namespace.N<You may wonder why
-< anyone would want to do this. We wonder the same thing, but Perl 5 does
-< it all the time. The Perl 6 implementation on Parrot includes type
-< sigils in the names of the variables it stores in namespaces so each
-< name is unique, e.g. C<$bee>, C<@bee>....>
----
-> <p>The first two statements in this example create a <code>String</code> PMC in <code>$P0</code> and assign it a value. In the third statement, <code>set_global</code> stores that PMC as the named global variable <code>bee</code>. At some later point in the program, <code>get_global</code> retrieves the global variable by name, and stores it in <code>$P1</code> to print.</p>
-> 
-> <p>Namespaces can only store PMC variables. Parrot boxes all primitive integer, number, or string values into the corresponding PMCs before storing them in a namespace.</p>
-> 
-> <p>The name of every variable stored in a particular namespace must be unique. You can&#39;t have store both an <code>Integer</code> PMC and an array PMC both named &#34;bee&#34;, stored in the same namespace.You may wonder why anyone would want to do this. We wonder the same thing, but Perl 5 does it all the time. The Perl 6 implementation on Parrot includes type sigils in the names of the variables it stores in namespaces so each name is unique, e.g. <code>$bee</code>, <code>@bee</code>....</p>
-1149,1150c1023,1027
-< X<hierarchical namespaces>
-< X<namespaces; hierarchy>
----
-> <p><!--
->       INDEX: hierarchical namespaces
-> --> <!--
->       INDEX: namespaces; hierarchy
-> --></p>
-1152,1162c1029,1031
-< A single global namespace would be far too limiting for most languages or
-< applications. The risk of accidental collisions -- where two libraries try to
-< use the same name for some variable -- would be quite high for larger code
-< bases. Parrot maintains a collection of namespaces arranged as a tree, with the
-< C<parrot> namespace as the root.  Every namespace you declare is a child of the
-< C<parrot> namespace (or a child of a child....).
-< 
-< The C<set_global> and C<get_global> opcodes both have alternate forms that take
-< a key name to access a variable in a particular namespace within the tree. This
-< code example stores a variable as C<bill> in the Duck namespace and retrieves
-< it again:
----
-> <p>A single global namespace would be far too limiting for most languages or applications. The risk of accidental collisions &#45;&#45; where two libraries try to use the same name for some variable &#45;&#45; would be quite high for larger code bases. Parrot maintains a collection of namespaces arranged as a tree, with the <code>parrot</code> namespace as the root. Every namespace you declare is a child of the <code>parrot</code> namespace (or a child of a child....).</p>
-> 
-> <p>The <code>set_global</code> and <code>get_global</code> opcodes both have alternate forms that take a key name to access a variable in a particular namespace within the tree. This code example stores a variable as <code>bill</code> in the Duck namespace and retrieves it again:</p>
-1166,1168c1035
-< The key name for the namespace can have multiple levels, which correspond to
-< levels in the namespace hierarchy. This example stores a variable as C<bill> in
-< the Electric namespace under the General namespace in the hierarchy.
----
-> <p>The key name for the namespace can have multiple levels, which correspond to levels in the namespace hierarchy. This example stores a variable as <code>bill</code> in the Electric namespace under the General namespace in the hierarchy.</p>
-1172,1173c1039,1043
-< X<root namespace>
-< X<namespaces; root>
----
-> <p><!--
->       INDEX: root namespace
-> --> <!--
->       INDEX: namespaces; root
-> --></p>
-1175,1181c1045,1047
-< The C<set_global> and C<get_global> opcode operate on the currently selected
-< namespace. The default top-level namespace is the "root" namespace. The
-< C<.namespace>X<.namespace directive> directive allows you to declare any
-< namespace for subsequent code.  If you select the General Electric
-< namespace, then store or retrieve the C<bill> variable without
-< specifying a namespace, you will work with the General Electric bill,
-< not the Duck bill.
----
-> <p>The <code>set_global</code> and <code>get_global</code> opcode operate on the currently selected namespace. The default top&#45;level namespace is the &#34;root&#34; namespace. The <code>.namespace</code><!--
->       INDEX: .namespace directive
-> --> directive allows you to declare any namespace for subsequent code. If you select the General Electric namespace, then store or retrieve the <code>bill</code> variable without specifying a namespace, you will work with the General Electric bill, not the Duck bill.</p>
-1183c1049
-<   .namespace ["General";"Electric"]
----
-> <pre>  .namespace [&#34;General&#34;;&#34;Electric&#34;]
-1185,1191c1051,1052
-<   set_global "bill", $P0
-<   $P1 = get_global "bill"
-< 
-< 
-< Passing an empty key to the C<.namespace> directive resets the selected
-< namespace to the root namespace. The brackets are required even when the
-< key is empty.
----
->   set_global &#34;bill&#34;, $P0
->   $P1 = get_global &#34;bill&#34;</pre>
-1193c1054
-<   .namespace [ ]
----
-> <p>Passing an empty key to the <code>.namespace</code> directive resets the selected namespace to the root namespace. The brackets are required even when the key is empty.</p>
-1194a1056
-> <pre>  .namespace [ ]</pre>
-1196,1202c1058,1062
-< When you need to be absolutely sure you're working with the root namespace
-< regardless of what namespace is currently active, use the
-< C<set_root_global>X<set_root_global opcode> and
-< C<get_root_global>X<get_root_global opcode> opcodes instead of
-< C<set_global> and C<get_global>. This example sets and retrieves the
-< variable C<bill> in the Dollar namespace, which is directly under the
-< root namespace:
----
-> <p>When you need to be absolutely sure you&#39;re working with the root namespace regardless of what namespace is currently active, use the <code>set_root_global</code><!--
->       INDEX: set_root_global opcode
-> --> and <code>get_root_global</code><!--
->       INDEX: get_root_global opcode
-> --> opcodes instead of <code>set_global</code> and <code>get_global</code>. This example sets and retrieves the variable <code>bill</code> in the Dollar namespace, which is directly under the root namespace:</p>
-1206,1222c1066,1080
-< X<HLL namespaces>
-< X<namespaces; hll>
-< To prevent further collisions, each high-level language running on
-< Parrot operates within its own virtual namespace root. The default
-< virtual root is C<parrot>, and the C<.HLL>X<.HLL directive> directive
-< (for I<H>igh-I<L>evel I<L>anguage) selects an alternate virtual root for
-< a particular high-level language:
-< 
-<   .HLL 'ruby'
-< 
-< 
-< The C<set_hll_global>X<set_hll_global opcode> and
-< C<get_hll_global>X<get_hll_global opcode> opcodes are like
-< C<set_root_global> and C<get_root_global>, except they always operate on
-< the virtual root for the currently selected HLL. This example stores and
-< retrieves a C<bill> variable in the Euro namespace, under the Dutch HLL
-< namespace root:
----
-> <p><!--
->       INDEX: HLL namespaces
-> --> <!--
->       INDEX: namespaces; hll
-> --> To prevent further collisions, each high&#45;level language running on Parrot operates within its own virtual namespace root. The default virtual root is <code>parrot</code>, and the <code>.HLL</code><!--
->       INDEX: .HLL directive
-> --> directive (for <i>H</i>igh&#45;<i>L</i>evel <i>L</i>anguage) selects an alternate virtual root for a particular high&#45;level language:</p>
-> 
-> <pre>  .HLL &#39;ruby&#39;</pre>
-> 
-> <p>The <code>set_hll_global</code><!--
->       INDEX: set_hll_global opcode
-> --> and <code>get_hll_global</code><!--
->       INDEX: get_hll_global opcode
-> --> opcodes are like <code>set_root_global</code> and <code>get_root_global</code>, except they always operate on the virtual root for the currently selected HLL. This example stores and retrieves a <code>bill</code> variable in the Euro namespace, under the Dutch HLL namespace root:</p>
-1224c1082
-<   .HLL 'Dutch'
----
-> <pre>  .HLL &#39;Dutch&#39;
-1226,1228c1084,1085
-<   set_hll_global ["Euro"], "bill", $P0
-<   $P1 = get_hll_global ["Euro"], "bill"
-< 
----
->   set_hll_global [&#34;Euro&#34;], &#34;bill&#34;, $P0
->   $P1 = get_hll_global [&#34;Euro&#34;], &#34;bill&#34;</pre>
-1233,1265c1090,1094
-< X<NameSpace PMC>
-< Namespaces are just PMCs. They implement the standard vtable functions
-< and a few extra methods. The C<get_namespace>X<get_namespace opcode>
-< opcode retrieves the currently selected namespace as a PMC object:
-< 
-<   $P0 = get_namespace
-< 
-< 
-< The C<get_root_namespace>X<get_root_namespace opcode> opcode retrieves
-< the namespace object for the root namespace.  The
-< C<get_hll_namespace>X<get_hll_namespace opcode> opcode retrieves the
-< virtual root for the currently selected HLL.
-< 
-<   $P0 = get_root_namespace
-<   $P0 = get_hll_namespace
-< 
-< 
-< Each of these three opcodes can take a key argument to retrieve a namespace
-< under the currenly selected namespace, root namespace, or HLL root namespace:
-< 
-<   $P0 = get_namespace ["Duck"]
-<   $P0 = get_root_namespace ["General";"Electric"]
-<   $P0 = get_hll_namespace ["Euro"]
-< 
-< 
-< Once you have a namespace object you can use it to retrieve variables from the
-< namespace instead of using a keyed lookup. This example first looks up the Euro
-< namespace in the currently selected HLL, then retrieves the C<bill> variable
-< from that namespace:
-< 
-<   $P0 = get_hll_namespace ["Euro"]
-<   $P1 = get_global $P0, "bill"
-< 
----
-> <p><!--
->       INDEX: NameSpace PMC
-> --> Namespaces are just PMCs. They implement the standard vtable functions and a few extra methods. The <code>get_namespace</code><!--
->       INDEX: get_namespace opcode
-> --> opcode retrieves the currently selected namespace as a PMC object:</p>
-1267,1270c1096
-< Namespaces also provide a set of methods to provide more complex
-< behavior than the standard vtable functions allow. The
-< C<get_name>X<get_name method> method returns the name of the namespace
-< as a C<ResizableStringArray>:
----
-> <pre>  $P0 = get_namespace</pre>
-1272c1098,1102
-<   $P3 = $P0.'get_name'()
----
-> <p>The <code>get_root_namespace</code><!--
->       INDEX: get_root_namespace opcode
-> --> opcode retrieves the namespace object for the root namespace. The <code>get_hll_namespace</code><!--
->       INDEX: get_hll_namespace opcode
-> --> opcode retrieves the virtual root for the currently selected HLL.</p>
-1273a1104,1105
-> <pre>  $P0 = get_root_namespace
->   $P0 = get_hll_namespace</pre>
-1275,1276c1107
-< The C<get_parent>X<get_parent method> method retrieves a namespace
-< object for the parent namespace that contains this one:
----
-> <p>Each of these three opcodes can take a key argument to retrieve a namespace under the currenly selected namespace, root namespace, or HLL root namespace:</p>
-1278c1109,1111
-<   $P5 = $P0.'get_parent'()
----
-> <pre>  $P0 = get_namespace [&#34;Duck&#34;]
->   $P0 = get_root_namespace [&#34;General&#34;;&#34;Electric&#34;]
->   $P0 = get_hll_namespace [&#34;Euro&#34;]</pre>
-1279a1113
-> <p>Once you have a namespace object you can use it to retrieve variables from the namespace instead of using a keyed lookup. This example first looks up the Euro namespace in the currently selected HLL, then retrieves the <code>bill</code> variable from that namespace:</p>
-1281,1282c1115,1116
-< The C<get_class>X<get_class method> method retrieves any Class PMC
-< associated with the namespace:
----
-> <pre>  $P0 = get_hll_namespace [&#34;Euro&#34;]
->   $P1 = get_global $P0, &#34;bill&#34;</pre>
-1284c1118,1120
-<   $P6 = $P0.'get_class'()
----
-> <p>Namespaces also provide a set of methods to provide more complex behavior than the standard vtable functions allow. The <code>get_name</code><!--
->       INDEX: get_name method
-> --> method returns the name of the namespace as a <code>ResizableStringArray</code>:</p>
-1285a1122
-> <pre>  $P3 = $P0.&#39;get_name&#39;()</pre>
-1287,1289c1124,1126
-< The C<add_var>X<add_var method> and C<find_var>X<find_var method>
-< methods store and retrieve variables in a namespace in a
-< language-neutral way:
----
-> <p>The <code>get_parent</code><!--
->       INDEX: get_parent method
-> --> method retrieves a namespace object for the parent namespace that contains this one:</p>
-1291,1292c1128
-<   $P0.'add_var'("bee", $P3)
-<   $P1 = $P0.'find_var'("bee")
----
-> <pre>  $P5 = $P0.&#39;get_parent&#39;()</pre>
-1293a1130,1132
-> <p>The <code>get_class</code><!--
->       INDEX: get_class method
-> --> method retrieves any Class PMC associated with the namespace:</p>
-1295,1296c1134
-< The C<find_namespace>X<find_namespace method> method looks up a
-< namespace, just like the C<get_namespace> opcode:
----
-> <pre>  $P6 = $P0.&#39;get_class&#39;()</pre>
-1298c1136,1140
-<   $P1 = $P0.'find_namespace'("Duck")
----
-> <p>The <code>add_var</code><!--
->       INDEX: add_var method
-> --> and <code>find_var</code><!--
->       INDEX: find_var method
-> --> methods store and retrieve variables in a namespace in a language&#45;neutral way:</p>
-1299a1142,1143
-> <pre>  $P0.&#39;add_var&#39;(&#34;bee&#34;, $P3)
->   $P1 = $P0.&#39;find_var&#39;(&#34;bee&#34;)</pre>
-1301,1302c1145,1147
-< The C<add_namespace>X<add_namespace method> method adds a new namespace
-< as a child of the namespace object:
----
-> <p>The <code>find_namespace</code><!--
->       INDEX: find_namespace method
-> --> method looks up a namespace, just like the <code>get_namespace</code> opcode:</p>
-1304c1149
-<   $P0.'add_namespace'($P1)
----
-> <pre>  $P1 = $P0.&#39;find_namespace&#39;(&#34;Duck&#34;)</pre>
-1305a1151,1153
-> <p>The <code>add_namespace</code><!--
->       INDEX: add_namespace method
-> --> method adds a new namespace as a child of the namespace object:</p>
-1307,1310c1155
-< The C<make_namespace>X<make_namespace method> method looks up a
-< namespace as a child of the namespace object and returns it. If the
-< requested namespace doesn't exist, C<make_namespace> creates a new one
-< and adds it under that name:
----
-> <pre>  $P0.&#39;add_namespace&#39;($P1)</pre>
-1312c1157,1159
-<   $P1 = $P0.'make_namespace'("Duck")
----
-> <p>The <code>make_namespace</code><!--
->       INDEX: make_namespace method
-> --> method looks up a namespace as a child of the namespace object and returns it. If the requested namespace doesn&#39;t exist, <code>make_namespace</code> creates a new one and adds it under that name:</p>
-1313a1161
-> <pre>  $P1 = $P0.&#39;make_namespace&#39;(&#34;Duck&#34;)</pre>
-1318,1322c1166,1168
-< X<aliasing>
-< Just like regular assignment, the various operations to store a variable in a
-< namespace only store a pointer to the PMC. If you modify the local PMC after
-< storing in a namespace, those changes will also appear in the stored global. To
-< store a true copy of the PMC, C<clone> it before you store it.
----
-> <p><!--
->       INDEX: aliasing
-> --> Just like regular assignment, the various operations to store a variable in a namespace only store a pointer to the PMC. If you modify the local PMC after storing in a namespace, those changes will also appear in the stored global. To store a true copy of the PMC, <code>clone</code> it before you store it.</p>
-1324,1325c1170
-< Leaving the global variable as an alias for a local variable has its advantages.
-< If you retrieve a stored global into a register and modify it:
----
-> <p>Leaving the global variable as an alias for a local variable has its advantages. If you retrieve a stored global into a register and modify it:</p>
-1329,1330c1174
-< ... you modify the value of the stored global, so you don't need to call
-< C<set_global> again.
----
-> <p>... you modify the value of the stored global, so you don&#39;t need to call <code>set_global</code> again.</p>
-1334c1178
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch05_control_structures.pod.html parrot-trunk/docs/html/docs/book/pir/ch05_control_structures.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Control Structures</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Control Structures
-302c302
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch06_subroutines.pod.html parrot-trunk/docs/html/docs/book/pir/ch06_subroutines.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Subroutines</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Subroutines
-759c759
-< --> Native Call Interface (NCI) is a special version of the Parrot calling conventions for calling functions in shared C libraries with a known signature. This is a simplified version of the first test in <em>t/pmc/nci.t</em>:</p>
----
-> --> Native Call Interface (NCI) is a special version of the Parrot calling conventions for calling functions in shared C libraries with a known signature. This is a simplified version of the first test in <em><a href="../../../t/pmc/nci.t.html">t/pmc/nci.t</a></em>:</p>
-789c789
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch07_objects.pod.html parrot-trunk/docs/html/docs/book/pir/ch07_objects.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Classes and Objects</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Classes and Objects
-341c341
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch08_io.pod.html parrot-trunk/docs/html/docs/book/pir/ch08_io.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - I/O</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; I/O
-368c368
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/book/pir/ch09_exceptions.pod.html parrot-trunk/docs/html/docs/book/pir/ch09_exceptions.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Exceptions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; Exceptions
-277c277
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/compiler_faq.pod.html parrot-trunk/docs/html/docs/compiler_faq.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot FAQ for compiler writers in PIR</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Parrot FAQ for compiler writers in PIR
-302c302
-< See also <em>t/dynpmc/dynlexpad.t</em>.</p>
----
-> See also <em><a href="../t/dynpmc/dynlexpad.t.html">t/dynpmc/dynlexpad.t</a></em>.</p>
-636c636
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/configuration.pod.html parrot-trunk/docs/html/docs/configuration.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Configuration System</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; Parrot Configuration System
-55c55
-< you would add the code used to determine its size in <em>config/auto/sizes.pm</em>.
----
-> you would add the code used to determine its size in <em><a href="../config/auto/sizes.pm.html">config/auto/sizes.pm</a></em>.
-83c83
-< To enable them run <em>Configure.pl</em> with the <code>&#45;&#45;ask</code> option.</p>
----
-> To enable them run <em><a href="../Configure.pl.html">Configure.pl</a></em> with the <code>&#45;&#45;ask</code> option.</p>
-118,119c118,119
-< the <em>Configure.pl</em> script.
-< The system is invoked by instantiating a <a href='TODO'>Parrot::Configure</a> object,
----
-> the <em><a href="../Configure.pl.html">Configure.pl</a></em> script.
-> The system is invoked by instantiating a <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object,
-131c131
-< the step <em>config/init/defaults.pm</em> uses the <code>init::defaults</code> namespace.</p>
----
-> the step <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em> uses the <code>init::defaults</code> namespace.</p>
-133c133
-< <p>Each step inherits its constructor and some other methods from <em>lib/Parrot/Configure/Step.pm</em>.
----
-> <p>Each step inherits its constructor and some other methods from <em><a href="../lib/Parrot/Configure/Step.pm.html">lib/Parrot/Configure/Step.pm</a></em>.
-167c167
-< <p>The configuration system won&#39;t execute your step by default unless it&#39;s specifically told to. To do this, edit <em>lib/Parrot/Configure/Step/List.pm</em>. Steps are run in the order in which that are registered with the <a href='TODO'>Parrot::Configure</a> object.</p>
----
-> <p>The configuration system won&#39;t execute your step by default unless it&#39;s specifically told to. To do this, edit <em><a href="../lib/Parrot/Configure/Step/List.pm.html">lib/Parrot/Configure/Step/List.pm</a></em>. Steps are run in the order in which that are registered with the <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object.</p>
-169c169
-< <p>Various utility functions for configuration steps are provided by the <a href='TODO'>Parrot::Configure::Utils</a> module.</p>
----
-> <p>Various utility functions for configuration steps are provided by the <a href='..%2Flib%2FParrot%2FConfigure%2FUtils.pm.html'>Parrot::Configure::Utils</a> module.</p>
-210c210
-< <p>Command&#45;line arguments are now processed by <code>process_options()</code>, a subroutine exported by <a href='TODO'>Parrot::Configure::Options</a>. If you add a new option, don&#39;t forget to add it to this documentation and to appropriate locations. Most options should be added to <code>@shared_valid_options</code> in <em>lib/Parrot/Configure/Options/Conf/Shared.pm</em>.</p>
----
-> <p>Command&#45;line arguments are now processed by <code>process_options()</code>, a subroutine exported by <a href='..%2Flib%2FParrot%2FConfigure%2FOptions.pm.html'>Parrot::Configure::Options</a>. If you add a new option, don&#39;t forget to add it to this documentation and to appropriate locations. Most options should be added to <code>@shared_valid_options</code> in <em><a href="../lib/Parrot/Configure/Options/Conf/Shared.pm.html">lib/Parrot/Configure/Options/Conf/Shared.pm</a></em>.</p>
-212c212
-< <p>Arguments passed to <em>Configure.pl</em> are held in a <a href='TODO'>Parrot::Configure::Data</a> object stored inside the <a href='TODO'>Parrot::Configure</a> object. The options data object may be accessed via the <code>Parrot::Configure::options()</code> method.</p>
----
-> <p>Arguments passed to <em><a href="../Configure.pl.html">Configure.pl</a></em> are held in a <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> object stored inside the <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object. The options data object may be accessed via the <code>Parrot::Configure::options()</code> method.</p>
-217c217
-< <p>As an alternative to typing a long string of options on the command&#45;line, Parrot can now be configured from a configuration file. You put the options in a configuration file, then call <em>Configure.pl</em> as follows:</p>
----
-> <p>As an alternative to typing a long string of options on the command&#45;line, Parrot can now be configured from a configuration file. You put the options in a configuration file, then call <em><a href="../Configure.pl.html">Configure.pl</a></em> as follows:</p>
-228c228
-< <p>The second step is <em>config/init/defaults.pm</em>, which sets up some defaults in a <a href='TODO'>Parrot::Configure::Data</a> object contained by the main <a href='TODO'>Parrot::Configure</a> object. It can be accessed via the <code>Parrot::Configure::data()</code> method. You get and set configuration system&#39;s data by interacting with this object. Some of its methods are summarized below.</p>
----
-> <p>The second step is <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em>, which sets up some defaults in a <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> object contained by the main <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object. It can be accessed via the <code>Parrot::Configure::data()</code> method. You get and set configuration system&#39;s data by interacting with this object. Some of its methods are summarized below.</p>
-245c245
-< Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system&#39;s data.See the <a href='TODO'>Parrot::Configure::Data</a> documentation for further details.</dl>
----
-> Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system&#39;s data.See the <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> documentation for further details.</dl>
-261c261
-< These settings are deleted before <em>lib/Parrot/Config.pm</em> is written. These entries are only used e.g. for Makefile creation.</dl>
----
-> These settings are deleted before <em><a href="../lib/Parrot/Config.pm.html">lib/Parrot/Config.pm</a></em> is written. These entries are only used e.g. for Makefile creation.</dl>
-266c266
-< <p>Parrot configuration is currently jump&#45;started by extracting considerable information from variables associated with the instance of Perl 5 which the user is using to run <em>Configure.pl</em>. These variables are largely looked up in the <code>%Config</code> found in the Perl 5 <em>Config.pm</em>, but may also be sought in Perl 5 special variables such as <code>$^O</code>. All such lookups should be done in configuration step <code>init::defaults</code> and <b>only</b> in that step. Special accessors are available for working with such variables; see <em>config/init/defaults.pm</em> and <em>lib/Parrot/Configure/Data.pm</em>.</p>
----
-> <p>Parrot configuration is currently jump&#45;started by extracting considerable information from variables associated with the instance of Perl 5 which the user is using to run <em><a href="../Configure.pl.html">Configure.pl</a></em>. These variables are largely looked up in the <code>%Config</code> found in the Perl 5 <em>Config.pm</em>, but may also be sought in Perl 5 special variables such as <code>$^O</code>. All such lookups should be done in configuration step <code>init::defaults</code> and <b>only</b> in that step. Special accessors are available for working with such variables; see <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em> and <em><a href="../lib/Parrot/Configure/Data.pm.html">lib/Parrot/Configure/Data.pm</a></em>.</p>
-276c276
-< <p><a href='TODO'>Parrot::Configure</a>, <a href='TODO'>Parrot::Configure::Data</a>, <a href='TODO'>Parrot::Configure::Utils</a>, <a href='TODO'>Parrot::Configure::Step</a></p>
----
-> <p><a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a>, <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a>, <a href='..%2Flib%2FParrot%2FConfigure%2FUtils.pm.html'>Parrot::Configure::Utils</a>, <a href='..%2Flib%2FParrot%2FConfigure%2FStep.pm.html'>Parrot::Configure::Step</a></p>
-280c280
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/debugger.pod.html parrot-trunk/docs/html/docs/debugger.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - The Parrot Debugger</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; The Parrot Debugger
-307c307
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/debug.pod.html parrot-trunk/docs/html/docs/debug.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Debugging Parrot</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; Debugging Parrot
-76c76
-< <p>See <em>docs/dev/infant.pod</em> for details of one frequent problem: infant mortality. Infant mortality is when you create a Parrot object, but the garbage collector runs before you put it into a Parrot register or in something else that is itself within a Parrot register.</p>
----
-> <p>See <em><a href="dev/infant.pod.html">docs/dev/infant.pod</a></em> for details of one frequent problem: infant mortality. Infant mortality is when you create a Parrot object, but the garbage collector runs before you put it into a Parrot register or in something else that is itself within a Parrot register.</p>
-88c88
-< <p>One possible tool is <code>parrot_debugger</code>, the Parrot Debugger. See <em>docs/debugger.pod</em> for details on it.</p>
----
-> <p>One possible tool is <code>parrot_debugger</code>, the Parrot Debugger. See <em><a href="debugger.pod.html">docs/debugger.pod</a></em> for details on it.</p>
-247c247
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/byteorder.pod.html parrot-trunk/docs/html/docs/dev/byteorder.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Byteorder Conversion Functions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Byteorder Conversion Functions
-54c54
-< <p>When reading a pbc stored in a different architecture, the pbc header defines the pbc byteorder for the architecture which stored the pbc, and the <em>src/packfile/pf_items.c</em> functions are used to convert the values to the native endianness, wordsize and ptrsize.</p>
----
-> <p>When reading a pbc stored in a different architecture, the pbc header defines the pbc byteorder for the architecture which stored the pbc, and the <em><a href="../../src/packfile/pf_items.c.html">src/packfile/pf_items.c</a></em> functions are used to convert the values to the native endianness, wordsize and ptrsize.</p>
-129c129
-< <p>The fetch and transformer functions are implemented in <em>src/packfile/pf_items.c</em></p>
----
-> <p>The fetch and transformer functions are implemented in <em><a href="../../src/packfile/pf_items.c.html">src/packfile/pf_items.c</a></em></p>
-133c133
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/c_functions.pod.html parrot-trunk/docs/html/docs/dev/c_functions.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - C function decoration guidelines</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; C function decoration guidelines
-214c214
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/debugging_with_msvc.pod.html parrot-trunk/docs/html/docs/dev/debugging_with_msvc.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Debugging Parrot with Microsoft</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Debugging Parrot with Microsoft
-161c161
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/events.pod.html parrot-trunk/docs/html/docs/dev/events.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Design Notes for Events</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Design Notes for Events
-152c152
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/headerizer.pod.html parrot-trunk/docs/html/docs/dev/headerizer.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - The Headerizer</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; The Headerizer
-39c39
-< <p>The Headerizer (<em>tools/build/headerizer.pl</em>) is a tool that generates chunks of <em>.h</em> header files based on C source code.</p>
----
-> <p>The Headerizer (<em><a href="../../tools/build/headerizer.pl.html">tools/build/headerizer.pl</a></em>) is a tool that generates chunks of <em>.h</em> header files based on C source code.</p>
-66c66
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/infant.pod.html parrot-trunk/docs/html/docs/dev/infant.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Infant Mortality</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Infant Mortality
-298c298
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/longopt.pod.html parrot-trunk/docs/html/docs/dev/longopt.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Long option parsing</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Long option parsing
-98c98
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/optimizer.pod.html parrot-trunk/docs/html/docs/dev/optimizer.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - About the IMCC optimizer</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; About the IMCC optimizer
-165c165
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/parrot_api.pod.html parrot-trunk/docs/html/docs/dev/parrot_api.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Notes on the PARROT_EXPORT macro</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Notes on the PARROT_EXPORT macro
-64c64
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/pccmethods.pod.html parrot-trunk/docs/html/docs/dev/pccmethods.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Calling Conventions in C</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Parrot Calling Conventions in C
-115c115
-< <p>That is, a register type, followed by a name, optionally followed by one or more flags specified as adverbs. The list of supported adverbs is listed in <em>docs/pdds/pdd03_calling_conventions.pod</em>, the calling conventions design document.</p>
----
-> <p>That is, a register type, followed by a name, optionally followed by one or more flags specified as adverbs. The list of supported adverbs is listed in <em><a href="../pdds/pdd03_calling_conventions.pod.html">docs/pdds/pdd03_calling_conventions.pod</a></em>, the calling conventions design document.</p>
-141c141
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/pcc_state.pod.html parrot-trunk/docs/html/docs/dev/pcc_state.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - parrot calling conventions state table</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; parrot calling conventions state table
-134c134
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/pmc_freeze.pod.html parrot-trunk/docs/html/docs/dev/pmc_freeze.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Freeze/Thaw Design Notes</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Freeze/Thaw Design Notes
-215c215
-< <p><em>src/pmc_freeze.c</em>, <em>pf/pf_items.c</em></p>
----
-> <p><em><a href="../../src/pmc_freeze.c.html">src/pmc_freeze.c</a></em>, <em>pf/pf_items.c</em></p>
-224c224
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/pmc_obj_design_meeting_notes.pod.html parrot-trunk/docs/html/docs/dev/pmc_obj_design_meeting_notes.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot PMC/Object Design Meeting Notes</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Parrot PMC/Object Design Meeting Notes
-190c190
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/dev/profiling.pod.html parrot-trunk/docs/html/docs/dev/profiling.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Name</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Name
-91c91
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/embed.pod.html parrot-trunk/docs/html/docs/embed.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot embedding system</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Parrot embedding system
-2224c2224
-< <p><em>src/main.c</em> and <em>t/src/*.t</em> for Parrot&#39;s use of the embedding system.</p>
----
-> <p><em><a href="../src/main.c.html">src/main.c</a></em> and <em>t/src/*.t</em> for Parrot&#39;s use of the embedding system.</p>
-2230c2230
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/gettingstarted.pod.html parrot-trunk/docs/html/docs/gettingstarted.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Developer FAQ</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Parrot Developer FAQ
-97c97
-< <p>There are a few categories of documentation, each with different intents. It&#39;ll probably help to be aware of them before you go digging in. I highly suggest you check out <em>/docs/pdds/pdd07_codingstd.pod</em> for guidelines on how documentation is supposed to be laid out. For now, here&#39;s the executive summary:</p>
----
-> <p>There are a few categories of documentation, each with different intents. It&#39;ll probably help to be aware of them before you go digging in. I highly suggest you check out <em><a href="pdds/pdd07_codingstd.pod.html">/docs/pdds/pdd07_codingstd.pod</a></em> for guidelines on how documentation is supposed to be laid out. For now, here&#39;s the executive summary:</p>
-170c170
-< <p>See <em>docs/submissions.pod</em> for details.</p>
----
-> <p>See <em><a href="submissions.pod.html">docs/submissions.pod</a></em> for details.</p>
-175c175
-< <p>See <em>docs/submissions.pod</em> for details.</p>
----
-> <p>See <em><a href="submissions.pod.html">docs/submissions.pod</a></em> for details.</p>
-184c184
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/glossary.pod.html parrot-trunk/docs/html/docs/glossary.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Glossary</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Parrot Glossary
-206c206
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/intro.pod.html parrot-trunk/docs/html/docs/intro.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - The Parrot Primer</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; The Parrot Primer
-181c181
-< <p>The first step to building Parrot is to run the <em>Configure.pl</em> program,
----
-> <p>The first step to building Parrot is to run the <em><a href="../Configure.pl.html">Configure.pl</a></em> program,
-399c399
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/memory_internals.pod.html parrot-trunk/docs/html/docs/memory_internals.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Memory Internals</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Memory Internals
-72c72
-< <p>See <em>docs/pdds/pdd09_gc.pod</em> for details about the garbage collector system.</p>
----
-> <p>See <em><a href="pdds/pdd09_gc.pod.html">docs/pdds/pdd09_gc.pod</a></em> for details about the garbage collector system.</p>
-160c160
-< <p>The <em>Configure.pl</em> option <code>&#45;&#45;gc</code> allows one to use either method.</p>
----
-> <p>The <em><a href="../Configure.pl.html">Configure.pl</a></em> option <code>&#45;&#45;gc</code> allows one to use either method.</p>
-221c221
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-Only in parrot-trunk/docs/html/docs: ops
-diff -r parrot/docs/html/docs/overview.pod.html parrot-trunk/docs/html/docs/overview.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - A Parrot Overview</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; A Parrot Overview
-159c159
-< <p>One interesting thing about vtables is that you can construct them dynamically. You can find out more about vtables in <em>docs/vtables.pod</em>.</p>
----
-> <p>One interesting thing about vtables is that you can construct them dynamically. You can find out more about vtables in <em><a href="vtables.pod.html">docs/vtables.pod</a></em>.</p>
-181c181
-< <p>The bytecode format is fully documented in <em>docs/parrotbyte.pod</em>.</p>
----
-> <p>The bytecode format is fully documented in <em><a href="parrotbyte.pod.html">docs/parrotbyte.pod</a></em>.</p>
-185c185
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-Only in parrot-trunk/docs/html/docs: packfile-c.pod.html
-diff -r parrot/docs/html/docs/parrotbyte.pod.html parrot-trunk/docs/html/docs/parrotbyte.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - The Parrot Bytecode (PBC) Format</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; The Parrot Bytecode (PBC) Format
-48c48
-< <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32&#45;bit) or 8 (64 bit). The bytecode loader is responsible for transforming the file into the VM native wordsize on the fly. For performance, a utility <em>pbc_dump</em> is provided to convert PBCs on disk if they cannot be recompiled. See <em>src/pbc_dump.c</em> for more information.</p>
----
-> <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32&#45;bit) or 8 (64 bit). The bytecode loader is responsible for transforming the file into the VM native wordsize on the fly. For performance, a utility <em>pbc_dump</em> is provided to convert PBCs on disk if they cannot be recompiled. See <em><a href="../src/pbc_dump.c.html">src/pbc_dump.c</a></em> for more information.</p>
-319c319
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/parrothist.pod.html parrot-trunk/docs/html/docs/parrothist.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Release History</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Parrot Release History
-158c158
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/parrot.pod.html parrot-trunk/docs/html/docs/parrot.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Parrot
-128c128
-< The list is archived at: <a href='http://groups.google.com/group/parrot&#45;dev/'><a href="http://groups.google.com/group/parrot&#45;dev/">http://groups.google.com/group/parrot&#45;dev/</a></a> Many people have contributed their time and expertise to the Parrot project; see the <em>CREDITS</em> file for details.</p>
----
-> The list is archived at: <a href='http://groups.google.com/group/parrot&#45;dev/'><a href="http://groups.google.com/group/parrot&#45;dev/">http://groups.google.com/group/parrot&#45;dev/</a></a> Many people have contributed their time and expertise to the Parrot project; see the <em><a href="../CREDITS.html">CREDITS</a></em> file for details.</p>
-147c147
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-Only in parrot-trunk/docs/html/docs: pct
-diff -r parrot/docs/html/docs/pdds/draft/pdd01_overview.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd01_overview.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 1: Overview</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 1: Overview
-306c306
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 5: Opcodes</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 5: Opcodes
-189c189
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd06_pasm.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd06_pasm.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 6: Parrot Assembly Language (PASM)</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 6: Parrot Assembly Language (PASM)
-168c168
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd08_keys.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd08_keys.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 8: PMC Keys</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 8: PMC Keys
-214c214
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd10_embedding.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd10_embedding.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD10: Embedding and Extending</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD10: Embedding and Extending
-260c260
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd11_extending.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd11_extending.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 11: Extending</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 11: Extending
-40c40
-< <p>$Revision: 48025 $</p>
----
-> <p>$Revision: 47669 $</p>
-326c326
-< <p><em>docs/glossary.pod</em></p>
----
-> <p><em><a href="../../glossary.pod.html">docs/glossary.pod</a></em></p>
-330c330
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd14_numbers.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd14_numbers.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 14: Numbers</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 14: Numbers
-489c489
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd16_native_call.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd16_native_call.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 16: Native Call Interface (NCI)</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 16: Native Call Interface (NCI)
-319c319
-< <p><em>t/pmc/nci.t</em>, <em>src/nci_test.c</em></p>
----
-> <p><em><a href="../../../t/pmc/nci.t.html">t/pmc/nci.t</a></em>, <em><a href="../../../src/nci_test.c.html">src/nci_test.c</a></em></p>
-323c323
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd29_compiler_tools.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd29_compiler_tools.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 29: Compiler Tools</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 29: Compiler Tools
-339c339
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd31_hll_interop.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd31_hll_interop.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 31: Inter&#45;Language Calling</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 31: Inter&#45;Language Calling
-373c373
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/draft/pdd31_hll.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd31_hll.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - [DRAFT] PDD 31: HLL Compilers and Libraries</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; [DRAFT] PDD 31: HLL Compilers and Libraries
-192c192
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd00_pdd.pod.html parrot-trunk/docs/html/docs/pdds/pdd00_pdd.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 0: Design Document Format</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 0: Design Document Format
-92c92
-< An example of the currently accepted layout is given in <em>docs/pdds/pdd_template.pod</em>,
----
-> An example of the currently accepted layout is given in <em><a href="pdd_template.pod.html">docs/pdds/pdd_template.pod</a></em>,
-177c177
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd03_calling_conventions.pod.html parrot-trunk/docs/html/docs/pdds/pdd03_calling_conventions.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 3: Calling Conventions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 3: Calling Conventions
-299c299
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd07_codingstd.pod.html parrot-trunk/docs/html/docs/pdds/pdd07_codingstd.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 7: Conventions and Guidelines for Parrot Source Code</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 7: Conventions and Guidelines for Parrot Source Code
-32c32
-< <p>$Revision: 47658 $</p>
----
-> <p>$Revision: 45652 $</p>
-410c410
-< <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
----
-> <p>The <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em> test checks that the files needing this property have it set.</p>
-423c423
-< <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
----
-> <p>The <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em> test checks that the files needing this property have it set.</p>
-428c428
-< <p>The <code>svn:eol&#45;style</code> property makes sure that whenever a file is checked out of subversion it has the correct end&#45;of&#45;line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol&#45;style</code> property set to <code>native</code>. However, this is not true for all files. Some input files to tests (such as the <code>*.input</code> and <code>*.output</code> files for PIR tests) need to have <code>LF</code> as their <code>svn:eol&#45;style</code> property. The current list of such files is described in <em>t/distro/file_metadata.t</em>.</p>
----
-> <p>The <code>svn:eol&#45;style</code> property makes sure that whenever a file is checked out of subversion it has the correct end&#45;of&#45;line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol&#45;style</code> property set to <code>native</code>. However, this is not true for all files. Some input files to tests (such as the <code>*.input</code> and <code>*.output</code> files for PIR tests) need to have <code>LF</code> as their <code>svn:eol&#45;style</code> property. The current list of such files is described in <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em>.</p>
-438c438
-< <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
----
-> <p>The <em><a href="../../t/distro/file_metadata.t.html">t/distro/file_metadata.t</a></em> test checks that the files needing this property have it set.</p>
-567,569c567,569
-< This inline Pod documentation is transformed to HTML with:
-< <pre>    $ make html</pre>
-< 
----
-> This inline Pod documentation is parsed to HTML by running:
-> <pre>    $ perl tools/docs/write_docs.pl &#45;&#45;delete</pre>
-> or: $ make html
-640c640
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd09_gc.pod.html parrot-trunk/docs/html/docs/pdds/pdd09_gc.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 9: Garbage Collection Subsystem</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 9: Garbage Collection Subsystem
-680c680
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd13_bytecode.pod.html parrot-trunk/docs/html/docs/pdds/pdd13_bytecode.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 13: Bytecode</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 13: Bytecode
-990c990
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd15_objects.pod.html parrot-trunk/docs/html/docs/pdds/pdd15_objects.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 15: Objects and Classes</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 15: Objects and Classes
-1273c1273
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd17_pmc.pod.html parrot-trunk/docs/html/docs/pdds/pdd17_pmc.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 17: Polymorphic Containers</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 17: Polymorphic Containers
-91c91
-< <p><code>_metadata</code> holds internal PMC metadata (properties). See the setprop/getprop ops in <em>docs/ops/pmc.pod</em>.</p>
----
-> <p><code>_metadata</code> holds internal PMC metadata (properties). See the setprop/getprop ops in <em><a href="../ops/pmc.pod.html">docs/ops/pmc.pod</a></em>.</p>
-797c797
-< Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating&#45;point number and store the remainder in <i>dest</i>. Note that <i>dest</i> may be the same PMC as <i>self</i>; in that case optimizations may be made. The <code>i_</code> variants perform an inplace operation, modifying the value of <i>self</i>.Note that <code>modulus</code> uses Knuth&#39;s &#34;corrected mod&#34; algorithm, as implemented in <em>src/utils.c</em>, while <code>cmodulus</code> uses the C&#45;style fmod function.
----
-> Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating&#45;point number and store the remainder in <i>dest</i>. Note that <i>dest</i> may be the same PMC as <i>self</i>; in that case optimizations may be made. The <code>i_</code> variants perform an inplace operation, modifying the value of <i>self</i>.Note that <code>modulus</code> uses Knuth&#39;s &#34;corrected mod&#34; algorithm, as implemented in <em><a href="../../src/utils.c.html">src/utils.c</a></em>, while <code>cmodulus</code> uses the C&#45;style fmod function.
-1228c1228
-< <p><em>docs/pmc2c.pod</em></p>
----
-> <p><em><a href="../pmc2c.pod.html">docs/pmc2c.pod</a></em></p>
-1232c1232
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd18_security.pod.html parrot-trunk/docs/html/docs/pdds/pdd18_security.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 18: Security Model</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 18: Security Model
-234c234
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd19_pir.pod.html parrot-trunk/docs/html/docs/pdds/pdd19_pir.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 19: Parrot Intermediate Representation (PIR)</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 19: Parrot Intermediate Representation (PIR)
-838c838
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd20_lexical_vars.pod.html parrot-trunk/docs/html/docs/pdds/pdd20_lexical_vars.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 20: Lexical Variables</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 20: Lexical Variables
-312c312
-< <p><em>t/op/lexicals.t</em></p>
----
-> <p><em><a href="../../t/op/lexicals.t.html">t/op/lexicals.t</a></em></p>
-316c316
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd21_namespaces.pod.html parrot-trunk/docs/html/docs/pdds/pdd21_namespaces.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 21: Namespaces</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 21: Namespaces
-436c436
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd22_io.pod.html parrot-trunk/docs/html/docs/pdds/pdd22_io.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 22: I/O</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 22: I/O
-755c755
-< <p><em>src/io/core.c</em>, <em>src/ops/io.ops</em>, <em>include/parrot/io.h</em>, <em>runtime/parrot/library/Stream/*</em>, <em>src/io/unix.c</em>, <em>src/io/win32.c</em>, Perl 5&#39;s IO::AIO, and POE</p>
----
-> <p><em><a href="../../src/io/core.c.html">src/io/core.c</a></em>, <em><a href="../../src/ops/io.ops.html">src/ops/io.ops</a></em>, <em>include/parrot/io.h</em>, <em>runtime/parrot/library/Stream/*</em>, <em><a href="../../src/io/unix.c.html">src/io/unix.c</a></em>, <em><a href="../../src/io/win32.c.html">src/io/win32.c</a></em>, Perl 5&#39;s IO::AIO, and POE</p>
-759c759
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd23_exceptions.pod.html parrot-trunk/docs/html/docs/pdds/pdd23_exceptions.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 23: Exceptions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 23: Exceptions
-425,428c425,428
-< <p><em>src/ops/core.ops</em>,
-< <em>src/exceptions.c</em>,
-< <em>src/pmc/exception.pmc</em>,
-< <em>src/pmc/exceptionhandler.pmc</em></p>
----
-> <p><em><a href="../../src/ops/core.ops.html">src/ops/core.ops</a></em>,
-> <em><a href="../../src/exceptions.c.html">src/exceptions.c</a></em>,
-> <em><a href="../../src/pmc/exception.pmc.html">src/pmc/exception.pmc</a></em>,
-> <em><a href="../../src/pmc/exceptionhandler.pmc.html">src/pmc/exceptionhandler.pmc</a></em></p>
-432c432
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd24_events.pod.html parrot-trunk/docs/html/docs/pdds/pdd24_events.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 24: Events</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 24: Events
-336c336
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd25_concurrency.pod.html parrot-trunk/docs/html/docs/pdds/pdd25_concurrency.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 25: Concurrency</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 25: Concurrency
-231c231
-< and a set of core routines in <em>src/scheduler.c</em>.</p>
----
-> and a set of core routines in <em><a href="../../src/scheduler.c.html">src/scheduler.c</a></em>.</p>
-437c437
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd26_ast.pod.html parrot-trunk/docs/html/docs/pdds/pdd26_ast.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 26: Compiler Tools &#45; Abstract Syntax Tree</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 26: Compiler Tools &#45; Abstract Syntax Tree
-374c374
-< The table of PIR opcodes that PAST &#34;knows&#34; about is given in <em>compilers/pct/src/PAST/Compiler.pir</em> .
----
-> The table of PIR opcodes that PAST &#34;knows&#34; about is given in <em><a href="../../compilers/pct/src/PAST/Compiler.pir.html">compilers/pct/src/PAST/Compiler.pir</a></em> .
-456c456
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd27_multiple_dispatch.pod.html parrot-trunk/docs/html/docs/pdds/pdd27_multiple_dispatch.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 27: Multiple Dispatch</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 27: Multiple Dispatch
-262c262
-< <p><em>docs/mmd.pod</em>, <em>src/multidispatch.c</em>, <em>src/pmc/multisub.pmc</em></p>
----
-> <p><em>docs/mmd.pod</em>, <em><a href="../../src/multidispatch.c.html">src/multidispatch.c</a></em>, <em><a href="../../src/pmc/multisub.pmc.html">src/pmc/multisub.pmc</a></em></p>
-266c266
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd28_strings.pod.html parrot-trunk/docs/html/docs/pdds/pdd28_strings.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 28: Strings</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 28: Strings
-739c739
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd30_install.pod.html parrot-trunk/docs/html/docs/pdds/pdd30_install.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PDD 30: Installation</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; PDD 30: Installation
-41c41
-< <p>$Revision: 48025 $</p>
----
-> <p>$Revision: 47917 $</p>
-120c120
-< <p>A new language is generated by <em>tools/dev/mk_language_shell.pl</em></p>
----
-> <p>A new language is generated by <em><a href="../../tools/dev/mk_language_shell.pl.html">tools/dev/mk_language_shell.pl</a></em></p>
-122c122
-< <p>The makefiles are generated from a makefile template, which can use conditional platform and config logic. The forward slashes are automatically converted to backslashes for MSWin32 and <code>\n</code> is converted to <code>\r\n</code> for MSWin32 nmake. See <a href='TODO'>Parrot::Configure::Compiler</a>.</p>
----
-> <p>The makefiles are generated from a makefile template, which can use conditional platform and config logic. The forward slashes are automatically converted to backslashes for MSWin32 and <code>\n</code> is converted to <code>\r\n</code> for MSWin32 nmake. See <a href='..%2F..%2Flib%2FParrot%2FConfigure%2FCompiler.pm.html'>Parrot::Configure::Compiler</a>.</p>
-136c136
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pdds/pdd_template.pod.html parrot-trunk/docs/html/docs/pdds/pdd_template.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Design Document Template</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> &raquo; Design Document Template
-85c85
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pmc/array.pod.html parrot-trunk/docs/html/docs/pmc/array.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Array base class</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Array base class
-135c135
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-Only in parrot-trunk/docs/html/docs/pmc: documentation.pod.html
-diff -r parrot/docs/html/docs/pmc/struct.pod.html parrot-trunk/docs/html/docs/pmc/struct.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Accessing C Structs from Parrot</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Accessing C Structs from Parrot
-286c286
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/pmc/subs.pod.html parrot-trunk/docs/html/docs/pmc/subs.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Subroutines</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; <a href="../../../html/developer.html">Developer Documentation</a> &raquo; Parrot Subroutines
-46c46
-< <p>Parrot comes with different subroutine and related classes which implement CPS (Continuation Passing Style) and PCC (Parrot Calling Conventions) <em>docs/pdds/pdd03_calling_conventions.pod</em>.</p>
----
-> <p>Parrot comes with different subroutine and related classes which implement CPS (Continuation Passing Style) and PCC (Parrot Calling Conventions) <em><a href="../pdds/pdd03_calling_conventions.pod.html">docs/pdds/pdd03_calling_conventions.pod</a></em>.</p>
-328c328
-< <p><em>src/pmc/sub.pmc</em>, <em>src/pmc/closure.pmc</em>, <em>src/pmc/continuation.pmc</em>, <em>src/pmc/coroutine.pmc</em>, <em>src/sub.c</em>, <em>t/pmc/sub.t</em></p>
----
-> <p><em><a href="../../src/pmc/sub.pmc.html">src/pmc/sub.pmc</a></em>, <em>src/pmc/closure.pmc</em>, <em><a href="../../src/pmc/continuation.pmc.html">src/pmc/continuation.pmc</a></em>, <em><a href="../../src/pmc/coroutine.pmc.html">src/pmc/coroutine.pmc</a></em>, <em><a href="../../src/sub.c.html">src/sub.c</a></em>, <em><a href="../../t/pmc/sub.t.html">t/pmc/sub.t</a></em></p>
-333c333
-< <p><em>docs/pdds/pdd03_calling_conventions.pod</em> <em>docs/pdds/pdd19_pir.pod</em></p>
----
-> <p><em><a href="../pdds/pdd03_calling_conventions.pod.html">docs/pdds/pdd03_calling_conventions.pod</a></em> <em><a href="../pdds/pdd19_pir.pod.html">docs/pdds/pdd19_pir.pod</a></em></p>
-342c342
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
 Only in parrot-trunk/docs/html/docs: pmc2c.pod.html
-diff -r parrot/docs/html/docs/porting_intro.pod.html parrot-trunk/docs/html/docs/porting_intro.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Subsystem Porting Introduction</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Parrot Subsystem Porting Introduction
+diff -r parrot-trunk/docs/html/docs/porting_intro.pod.html parrot/docs/html/docs/porting_intro.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Parrot Subsystem Porting Introduction
+---
+>                     Parrot Subsystem Porting Introduction
 67c67
-< <li><em>t/pmc/threads.t</em></li>
----
-> <li><em><a href="../t/pmc/threads.t.html">t/pmc/threads.t</a></em></li>
+< <li><em><a href="../t/pmc/threads.t.html">t/pmc/threads.t</a></em></li>
+---
+> <li><em>t/pmc/threads.t</em></li>
 71c71
-< <li><em>src/thread.c</em></li>
----
-> <li><em><a href="../src/thread.c.html">src/thread.c</a></em></li>
+< <li><em><a href="../src/thread.c.html">src/thread.c</a></em></li>
+---
+> <li><em>src/thread.c</em></li>
 104c104
-< <li><em>t/pmc/signal.t</em></li>
----
-> <li><em><a href="../t/pmc/signal.t.html">t/pmc/signal.t</a></em></li>
+< <li><em><a href="../t/pmc/signal.t.html">t/pmc/signal.t</a></em></li>
+---
+> <li><em>t/pmc/signal.t</em></li>
 164c164
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
 Only in parrot-trunk/docs/html/docs/project: metacommitter_guide.pod.html
 Only in parrot-trunk/docs/html/docs/project: release_manager_guide.pod.html
-diff -r parrot/docs/html/docs/project/roles_responsibilities.pod.html parrot-trunk/docs/html/docs/project/roles_responsibilities.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Roles and Responsibilities</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; Parrot Roles and Responsibilities
+diff -r parrot-trunk/docs/html/docs/project/roles_responsibilities.pod.html parrot/docs/html/docs/project/roles_responsibilities.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; Parrot Roles and Responsibilities
+---
+>                     Parrot Roles and Responsibilities
 60c60
-< <p>See <em>docs/project/release_manager_guide.pod</em> for more information.</p>
----
-> <p>See <em><a href="release_manager_guide.pod.html">docs/project/release_manager_guide.pod</a></em> for more information.</p>
+< <p>See <em><a href="release_manager_guide.pod.html">docs/project/release_manager_guide.pod</a></em> for more information.</p>
+---
+> <p>See <em>docs/project/release_manager_guide.pod</em> for more information.</p>
 71c71
-< <p>See <em>docs/project/metacommitter_guide.pod</em> for more information.</p>
----
-> <p>See <em><a href="metacommitter_guide.pod.html">docs/project/metacommitter_guide.pod</a></em> for more information.</p>
+< <p>See <em><a href="metacommitter_guide.pod.html">docs/project/metacommitter_guide.pod</a></em> for more information.</p>
+---
+> <p>See <em>docs/project/metacommitter_guide.pod</em> for more information.</p>
 175c175
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/project/support_policy.pod.html parrot-trunk/docs/html/docs/project/support_policy.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Release and Support Policy</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../html/index.html">Home</a> &raquo; Parrot Release and Support Policy
-109,110c109,117
-< though we&#39;re likely to stagger the removals.
-< An experimental feature that was never included in a supported release may be removed before a supported release without a deprecation cycle.</p>
----
-> though we&#39;re likely to stagger the removals.</p>
-> 
-> <h2><a name="Experimental_Features"
-> >Experimental Features</a></h2>
-> 
-> <p>From time to time,
-> we may add features to get feedback on their utility and design.
-> Marking them as &#34;Experimental&#34; in <em><a href="../../DEPRECATED.pod.html">DEPRECATED.pod</a></em> indicates that we may modify or remove them without official deprecation notices.
-> Use them at your own risk&#45;&#45;and please provide feedback through official channels if you use them successfully or otherwise.</p>
-213c220
-< <li>Items otherwise eligible but marked as &#34;experimental&#34; in <em>DEPRECATED.pod</em></li>
----
-> <li>Items otherwise eligible but marked as &#34;experimental&#34; in <em><a href="../../DEPRECATED.pod.html">DEPRECATED.pod</a></em></li>
-228c235
-< See <em>docs/parrothist.pod</em> for details about which existing releases were considered supported.</p>
----
-> See <em><a href="../parrothist.pod.html">docs/parrothist.pod</a></em> for details about which existing releases were considered supported.</p>
-232c239
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/running.pod.html parrot-trunk/docs/html/docs/running.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Running</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Running
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/project/support_policy.pod.html parrot/docs/html/docs/project/support_policy.pod.html
+23c23
+<                     <a href="../../../html/index.html">Home</a> &raquo; Parrot Release and Support Policy
+---
+>                     Parrot Release and Support Policy
+109,117c109,110
+< though we&#39;re likely to stagger the removals.</p>
+< 
+< <h2><a name="Experimental_Features"
+< >Experimental Features</a></h2>
+< 
+< <p>From time to time,
+< we may add features to get feedback on their utility and design.
+< Marking them as &#34;Experimental&#34; in <em><a href="../../DEPRECATED.pod.html">DEPRECATED.pod</a></em> indicates that we may modify or remove them without official deprecation notices.
+< Use them at your own risk&#45;&#45;and please provide feedback through official channels if you use them successfully or otherwise.</p>
+---
+> though we&#39;re likely to stagger the removals.
+> An experimental feature that was never included in a supported release may be removed before a supported release without a deprecation cycle.</p>
+220c213
+< <li>Items otherwise eligible but marked as &#34;experimental&#34; in <em><a href="../../DEPRECATED.pod.html">DEPRECATED.pod</a></em></li>
+---
+> <li>Items otherwise eligible but marked as &#34;experimental&#34; in <em>DEPRECATED.pod</em></li>
+235c228
+< See <em><a href="../parrothist.pod.html">docs/parrothist.pod</a></em> for details about which existing releases were considered supported.</p>
+---
+> See <em>docs/parrothist.pod</em> for details about which existing releases were considered supported.</p>
+239c232
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/running.pod.html parrot/docs/html/docs/running.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Running
+---
+>                     Running
+29c29
+< <p>Parrot &#45; Running</p>
+---
+> <p>docs/running.pod &#45; Running</p>
 107c107
-< See <em>docs/dev/optimizer.pod</em> for more information on the optimizer. Note that optimization is currently experimental and these options are likely to change.
----
-> See <em><a href="dev/optimizer.pod.html">docs/dev/optimizer.pod</a></em> for more information on the optimizer. Note that optimization is currently experimental and these options are likely to change.
+< See <em><a href="dev/optimizer.pod.html">docs/dev/optimizer.pod</a></em> for more information on the optimizer. Note that optimization is currently experimental and these options are likely to change.
+---
+> See <em>docs/dev/optimizer.pod</em> for more information on the optimizer. Note that optimization is currently experimental and these options are likely to change.
 236c236
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
 Only in parrot-trunk/docs/html/docs: stability.pod.html
-diff -r parrot/docs/html/docs/submissions.pod.html parrot-trunk/docs/html/docs/submissions.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Submission Instructions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Parrot Submission Instructions
+diff -r parrot-trunk/docs/html/docs/submissions.pod.html parrot/docs/html/docs/submissions.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Parrot Submission Instructions
+---
+>                     Parrot Submission Instructions
 41c41
-< create a bug report using the <em>parrotbug</em> utility.
----
-> create a bug report using the <em><a href="../parrotbug.html">parrotbug</a></em> utility.
+< create a bug report using the <em><a href="../parrotbug.html">parrotbug</a></em> utility.
+---
+> create a bug report using the <em>parrotbug</em> utility.
 91c91
-< Each and every patch is an important contribution to Parrot and it&#39;s important that these efforts are recognized. To that end, the <em>CREDITS</em> file contains an informal list of contributors and their contributions made to Parrot. Patch submitters are encouraged to include a new or updated entry for themselves in <em>CREDITS</em> as part of their patch.The format for entries in <em>CREDITS</em> is defined at the top of the file.</dl>
----
-> Each and every patch is an important contribution to Parrot and it&#39;s important that these efforts are recognized. To that end, the <em><a href="../CREDITS.html">CREDITS</a></em> file contains an informal list of contributors and their contributions made to Parrot. Patch submitters are encouraged to include a new or updated entry for themselves in <em><a href="../CREDITS.html">CREDITS</a></em> as part of their patch.The format for entries in <em><a href="../CREDITS.html">CREDITS</a></em> is defined at the top of the file.</dl>
+< Each and every patch is an important contribution to Parrot and it&#39;s important that these efforts are recognized. To that end, the <em><a href="../CREDITS.html">CREDITS</a></em> file contains an informal list of contributors and their contributions made to Parrot. Patch submitters are encouraged to include a new or updated entry for themselves in <em><a href="../CREDITS.html">CREDITS</a></em> as part of their patch.The format for entries in <em><a href="../CREDITS.html">CREDITS</a></em> is defined at the top of the file.</dl>
+---
+> Each and every patch is an important contribution to Parrot and it&#39;s important that these efforts are recognized. To that end, the <em>CREDITS</em> file contains an informal list of contributors and their contributions made to Parrot. Patch submitters are encouraged to include a new or updated entry for themselves in <em>CREDITS</em> as part of their patch.The format for entries in <em>CREDITS</em> is defined at the top of the file.</dl>
 227c227
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/tests.pod.html parrot-trunk/docs/html/docs/tests.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Testing Parrot</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; Testing Parrot
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/tests.pod.html parrot/docs/html/docs/tests.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/tools.html">Tools</a> &raquo; Testing Parrot
+---
+>                     Testing Parrot
 77c77
-< The Perl 5 module <code>Parrot::Test</code> and the PIR module <code>Test;More</code> help with writing tests.
----
-> The Perl 5 module <code><a href='../lib/Parrot/Test.pm.html'>Parrot::Test</a></code> and the PIR module <code>Test;More</code> help with writing tests.
+< The Perl 5 module <code><a href='../lib/Parrot/Test.pm.html'>Parrot::Test</a></code> and the PIR module <code>Test;More</code> help with writing tests.
+---
+> The Perl 5 module <code>Parrot::Test</code> and the PIR module <code>Test;More</code> help with writing tests.
 198c198
-< <p>The files in <em>t/postconfigure</em> are tests for build system. The build tools tests are intended to be run after someone has made changes in modules such as <em>lib/Parrot/Pmc2cUtils/</em>. They&#39;re set up to be run after <em>Configure.pl</em> has completed but before make has been invoked. (In fact, they will generate errors if make has completed.) You can run them with any of the following:</p>
----
-> <p>The files in <em>t/postconfigure</em> are tests for build system. The build tools tests are intended to be run after someone has made changes in modules such as <em>lib/Parrot/Pmc2cUtils/</em>. They&#39;re set up to be run after <em><a href="../Configure.pl.html">Configure.pl</a></em> has completed but before make has been invoked. (In fact, they will generate errors if make has completed.) You can run them with any of the following:</p>
+< <p>The files in <em>t/postconfigure</em> are tests for build system. The build tools tests are intended to be run after someone has made changes in modules such as <em>lib/Parrot/Pmc2cUtils/</em>. They&#39;re set up to be run after <em><a href="../Configure.pl.html">Configure.pl</a></em> has completed but before make has been invoked. (In fact, they will generate errors if make has completed.) You can run them with any of the following:</p>
+---
+> <p>The files in <em>t/postconfigure</em> are tests for build system. The build tools tests are intended to be run after someone has made changes in modules such as <em>lib/Parrot/Pmc2cUtils/</em>. They&#39;re set up to be run after <em>Configure.pl</em> has completed but before make has been invoked. (In fact, they will generate errors if make has completed.) You can run them with any of the following:</p>
 239c239
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/user/pir/exceptions.pod.html parrot-trunk/docs/html/docs/user/pir/exceptions.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Exceptions</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Exceptions
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/user/pir/exceptions.pod.html parrot/docs/html/docs/user/pir/exceptions.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Exceptions
+---
+>                     Exceptions
 127c127
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/user/pir/intro.pod.html parrot-trunk/docs/html/docs/user/pir/intro.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Writing PIR</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Writing PIR
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/user/pir/intro.pod.html parrot/docs/html/docs/user/pir/intro.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Writing PIR
+---
+>                     Writing PIR
 312c312
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/user/pir/objects.pod.html parrot-trunk/docs/html/docs/user/pir/objects.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Programming Parrot &#45;&#45; Using objects</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Programming Parrot &#45;&#45; Using objects
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/user/pir/objects.pod.html parrot/docs/html/docs/user/pir/objects.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Programming Parrot &#45;&#45; Using objects
+---
+>                     Programming Parrot &#45;&#45; Using objects
 424c424
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/user/pir/pmcs.pod.html parrot-trunk/docs/html/docs/user/pir/pmcs.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Programming Parrot &#45;&#45; PMCs</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Programming Parrot &#45;&#45; PMCs
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/user/pir/pmcs.pod.html parrot/docs/html/docs/user/pir/pmcs.pod.html
+23c23
+<                     <a href="../../../../html/index.html">Home</a> &raquo; <a href="../../../../html/developer.html">Developer Documentation</a> &raquo; Programming Parrot &#45;&#45; PMCs
+---
+>                     Programming Parrot &#45;&#45; PMCs
 274c274
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/docs/vtables.pod.html parrot-trunk/docs/html/docs/vtables.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Parrot Vtables</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Parrot Vtables
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/docs/vtables.pod.html parrot/docs/html/docs/vtables.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; <a href="../../html/developer.html">Developer Documentation</a> &raquo; Parrot Vtables
+---
+>                     Parrot Vtables
 75c75
-< <p>You should almost always start by running <em>tools/dev/gen_class.pl</em> to generate a skeleton for the class. Let&#39;s generate a number type for the beautifully non&#45;existent Fooby language:</p>
----
-> <p>You should almost always start by running <em><a href="../tools/dev/gen_class.pl.html">tools/dev/gen_class.pl</a></em> to generate a skeleton for the class. Let&#39;s generate a number type for the beautifully non&#45;existent Fooby language:</p>
+< <p>You should almost always start by running <em><a href="../tools/dev/gen_class.pl.html">tools/dev/gen_class.pl</a></em> to generate a skeleton for the class. Let&#39;s generate a number type for the beautifully non&#45;existent Fooby language:</p>
+---
+> <p>You should almost always start by running <em>tools/dev/gen_class.pl</em> to generate a skeleton for the class. Let&#39;s generate a number type for the beautifully non&#45;existent Fooby language:</p>
 79c79
-< <p>This will produce a skeleton PMC file (to be preprocessed into ordinary C code by the <em>tools/build/pmc2c.pl</em> program) with stubs for all the methods you need to fill in. Actually, there are more stubs here then you probably <i>need</i> to fill in. Your PMC isn&#39;t going to want to support all these methods, and in many cases you may want to fall back to default behavior instead of implementing a dummy method.&#62; The function <code>init</code> allows you to set up anything you need to set up.</p>
----
-> <p>This will produce a skeleton PMC file (to be preprocessed into ordinary C code by the <em><a href="../tools/build/pmc2c.pl.html">tools/build/pmc2c.pl</a></em> program) with stubs for all the methods you need to fill in. Actually, there are more stubs here then you probably <i>need</i> to fill in. Your PMC isn&#39;t going to want to support all these methods, and in many cases you may want to fall back to default behavior instead of implementing a dummy method.&#62; The function <code>init</code> allows you to set up anything you need to set up.</p>
+< <p>This will produce a skeleton PMC file (to be preprocessed into ordinary C code by the <em><a href="../tools/build/pmc2c.pl.html">tools/build/pmc2c.pl</a></em> program) with stubs for all the methods you need to fill in. Actually, there are more stubs here then you probably <i>need</i> to fill in. Your PMC isn&#39;t going to want to support all these methods, and in many cases you may want to fall back to default behavior instead of implementing a dummy method.&#62; The function <code>init</code> allows you to set up anything you need to set up.</p>
+---
+> <p>This will produce a skeleton PMC file (to be preprocessed into ordinary C code by the <em>tools/build/pmc2c.pl</em> program) with stubs for all the methods you need to fill in. Actually, there are more stubs here then you probably <i>need</i> to fill in. Your PMC isn&#39;t going to want to support all these methods, and in many cases you may want to fall back to default behavior instead of implementing a dummy method.&#62; The function <code>init</code> allows you to set up anything you need to set up.</p>
 93c93
-< <li>Run <code>make realclean</code>, and then run <em>Configure.pl</em> to add your new PMC to the set of built&#45;in PMCs.</li>
----
-> <li>Run <code>make realclean</code>, and then run <em><a href="../Configure.pl.html">Configure.pl</a></em> to add your new PMC to the set of built&#45;in PMCs.</li>
+< <li>Run <code>make realclean</code>, and then run <em><a href="../Configure.pl.html">Configure.pl</a></em> to add your new PMC to the set of built&#45;in PMCs.</li>
+---
+> <li>Run <code>make realclean</code>, and then run <em>Configure.pl</em> to add your new PMC to the set of built&#45;in PMCs.</li>
 99c99
-< <p>The usual way to continue from the <em>tools/dev/gen_class.pl</em>&#45;generated skeleton is to define a structure that will hook onto the <code>data</code>, if your data type needs to use that, and then also define some user&#45;defined flags.</p>
----
-> <p>The usual way to continue from the <em><a href="../tools/dev/gen_class.pl.html">tools/dev/gen_class.pl</a></em>&#45;generated skeleton is to define a structure that will hook onto the <code>data</code>, if your data type needs to use that, and then also define some user&#45;defined flags.</p>
+< <p>The usual way to continue from the <em><a href="../tools/dev/gen_class.pl.html">tools/dev/gen_class.pl</a></em>&#45;generated skeleton is to define a structure that will hook onto the <code>data</code>, if your data type needs to use that, and then also define some user&#45;defined flags.</p>
+---
+> <p>The usual way to continue from the <em>tools/dev/gen_class.pl</em>&#45;generated skeleton is to define a structure that will hook onto the <code>data</code>, if your data type needs to use that, and then also define some user&#45;defined flags.</p>
 127c127
-< <p>The master list of VTABLE interfaces can be found in <em>src/vtable.tbl</em> in the root directory of the Parrot source, with documentation in <em>docs/pdds/pdd17_pmc.pod</em>. A few of these are very important, for instance:</p>
----
-> <p>The master list of VTABLE interfaces can be found in <em>src/vtable.tbl</em> in the root directory of the Parrot source, with documentation in <em><a href="pdds/pdd17_pmc.pod.html">docs/pdds/pdd17_pmc.pod</a></em>. A few of these are very important, for instance:</p>
+< <p>The master list of VTABLE interfaces can be found in <em>src/vtable.tbl</em> in the root directory of the Parrot source, with documentation in <em><a href="pdds/pdd17_pmc.pod.html">docs/pdds/pdd17_pmc.pod</a></em>. A few of these are very important, for instance:</p>
+---
+> <p>The master list of VTABLE interfaces can be found in <em>src/vtable.tbl</em> in the root directory of the Parrot source, with documentation in <em>docs/pdds/pdd17_pmc.pod</em>. A few of these are very important, for instance:</p>
 222c222
-< <p>See the POD documentation in <em>tools/build/pmc2c.pl</em> for a list of useful keywords that you may use in the .pmc file.</p>
----
-> <p>See the POD documentation in <em><a href="../tools/build/pmc2c.pl.html">tools/build/pmc2c.pl</a></em> for a list of useful keywords that you may use in the .pmc file.</p>
+< <p>See the POD documentation in <em><a href="../tools/build/pmc2c.pl.html">tools/build/pmc2c.pl</a></em> for a list of useful keywords that you may use in the .pmc file.</p>
+---
+> <p>See the POD documentation in <em>tools/build/pmc2c.pl</em> for a list of useful keywords that you may use in the .pmc file.</p>
 226c226
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/DONORS.pod.html parrot-trunk/docs/html/DONORS.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - DONORS</title>
-23c23
-<                     Untitled
----
->                     <a href="../html/index.html">Home</a> &raquo; DONORS
-67c67
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/editor/README.pod.html parrot-trunk/docs/html/editor/README.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Productivity Comes in Pretty Colors</title>
-23c23
-<                     Untitled
----
->                     <a href="../../html/index.html">Home</a> &raquo; Productivity Comes in Pretty Colors
-43,52c43,48
-< <p>Calling <code>make vim&#45;install</code> in the <em>editor/</em> directory will install several files in <em>~/.vim</em>.
-< All these files have the <em>.vim</em> extension.
-< <em>pir.vim</em> (generated from <em>pir_vim.in</em>),
-< <em>pasm.vim</em>,
-< and <em>pmc.vim</em> are syntax files; <em>indent_pir.vim</em> is an indent plugin; and <em>filetype_parrot.vim</em> is a filetype script that tells vim to associate the extensions .pir,
-< .pasm,
-< and .pmc with the right syntax.
-< The syntax files are installed to <em>~/.vim/syntax/</em>; <em>filetype_parrot.vim</em> is installed to <em>~/.vim/ftdetect</em>; <em>indent_pir.vim</em> is copied to <em>~/.vim/indent/pir.vim</em>.
-< If you want indenting,
-< you should also place <code>filetype indent on</code> somewhere in your <em>~/.vimrc</em>.</p>
----
-> <p>By default calling <code>make vim&#45;install</code> in the <em>editor/</em> directory will install several files in <em>~/.vim</em>.
-> You can use the variable <code>VIM_DIR</code> on the command line by calling <code>make</code> to choose a different target directory for the vim files.</p>
-> 
-> <pre>   make vim&#45;install [VIM_DIR=/vim_files_target_directory]</pre>
-> 
-> <p>All these files have the <em>.vim</em> extension. <em>pir.vim</em> (generated from <em>pir_vim.in</em>), <em>pasm.vim</em>, and <em>pmc.vim</em> are syntax files; <em>indent_pir.vim</em> is an indent plugin; and <em>filetype_parrot.vim</em> is a filetype script that tells vim to associate the extensions .pir, .pasm, and .pmc with the right syntax. The syntax files are installed to <em>~/.vim/syntax/</em>; <em>filetype_parrot.vim</em> is installed to <em>~/.vim/parrot.vim</em>; <em>indent_pir.vim</em> is copied to <em>~/.vim/indent/pir.vim</em>. If you want indenting, you should also place <code>filetype indent on</code> somewhere in your <em>~/.vimrc</em>.</p>
-57,59c53
-< <p>There is a syntax file for the KDE editor Kate,
-< but it is not built by default.
-< Run:</p>
----
-> <p>There is a syntax file for the KDE editor Kate, but it is not built by default. Run:</p>
-65c59
-< <p>TODO: How do we install Kate syntax files?</p>
----
-> <p>Copy the file <em>imcc.xml</em> to <em>~/.kde/share/apps/katepart/syntax</em>.</p>
-123c117
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_1.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_1.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - PCT Tutorial Episode 1: Introduction</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; PCT Tutorial Episode 1: Introduction
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/DONORS.pod.html parrot/docs/html/DONORS.pod.html
+23c23
+<                     <a href="../html/index.html">Home</a> &raquo; DONORS
+---
+>                     DONORS
+25a26,30
+> <h1><a name="NAME"
+> >NAME</a></h1>
+> 
+> <p>DONORS</p>
+> 
+67c72
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/editor/README.pod.html parrot/docs/html/editor/README.pod.html
+23c23
+<                     <a href="../../html/index.html">Home</a> &raquo; Productivity Comes in Pretty Colors
+---
+>                     Productivity Comes in Pretty Colors
+43,48c43,52
+< <p>By default calling <code>make vim&#45;install</code> in the <em>editor/</em> directory will install several files in <em>~/.vim</em>.
+< You can use the variable <code>VIM_DIR</code> on the command line by calling <code>make</code> to choose a different target directory for the vim files.</p>
+< 
+< <pre>   make vim&#45;install [VIM_DIR=/vim_files_target_directory]</pre>
+< 
+< <p>All these files have the <em>.vim</em> extension. <em>pir.vim</em> (generated from <em>pir_vim.in</em>), <em>pasm.vim</em>, and <em>pmc.vim</em> are syntax files; <em>indent_pir.vim</em> is an indent plugin; and <em>filetype_parrot.vim</em> is a filetype script that tells vim to associate the extensions .pir, .pasm, and .pmc with the right syntax. The syntax files are installed to <em>~/.vim/syntax/</em>; <em>filetype_parrot.vim</em> is installed to <em>~/.vim/parrot.vim</em>; <em>indent_pir.vim</em> is copied to <em>~/.vim/indent/pir.vim</em>. If you want indenting, you should also place <code>filetype indent on</code> somewhere in your <em>~/.vimrc</em>.</p>
+---
+> <p>Calling <code>make vim&#45;install</code> in the <em>editor/</em> directory will install several files in <em>~/.vim</em>.
+> All these files have the <em>.vim</em> extension.
+> <em>pir.vim</em> (generated from <em>pir_vim.in</em>),
+> <em>pasm.vim</em>,
+> and <em>pmc.vim</em> are syntax files; <em>indent_pir.vim</em> is an indent plugin; and <em>filetype_parrot.vim</em> is a filetype script that tells vim to associate the extensions .pir,
+> .pasm,
+> and .pmc with the right syntax.
+> The syntax files are installed to <em>~/.vim/syntax/</em>; <em>filetype_parrot.vim</em> is installed to <em>~/.vim/ftdetect</em>; <em>indent_pir.vim</em> is copied to <em>~/.vim/indent/pir.vim</em>.
+> If you want indenting,
+> you should also place <code>filetype indent on</code> somewhere in your <em>~/.vimrc</em>.</p>
+53c57,59
+< <p>There is a syntax file for the KDE editor Kate, but it is not built by default. Run:</p>
+---
+> <p>There is a syntax file for the KDE editor Kate,
+> but it is not built by default.
+> Run:</p>
+59c65
+< <p>Copy the file <em>imcc.xml</em> to <em>~/.kde/share/apps/katepart/syntax</em>.</p>
+---
+> <p>TODO: How do we install Kate syntax files?</p>
+117c123
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_1.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_1.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; PCT Tutorial Episode 1: Introduction
+---
+>                     PCT Tutorial Episode 1: Introduction
 297c297
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_2.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_2.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 2: Poking in Compiler Guts</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 2: Poking in Compiler Guts
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_2.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_2.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 2: Poking in Compiler Guts
+---
+>                     Episode 2: Poking in Compiler Guts
 195c195
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_3.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_3.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 3: Squaak Details and First Steps</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 3: Squaak Details and First Steps
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_3.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_3.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 3: Squaak Details and First Steps
+---
+>                     Episode 3: Squaak Details and First Steps
 332c332
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_4.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_4.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 4: PAST Nodes and More Statements</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 4: PAST Nodes and More Statements
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_4.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_4.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 4: PAST Nodes and More Statements
+---
+>                     Episode 4: PAST Nodes and More Statements
 373c373
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_5.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_5.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 5: Variable Declaration and Scope</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 5: Variable Declaration and Scope
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_5.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_5.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 5: Variable Declaration and Scope
+---
+>                     Episode 5: Variable Declaration and Scope
 285c285
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_6.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_6.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 6: Scope and Subroutines</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 6: Scope and Subroutines
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_6.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_6.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 6: Scope and Subroutines
+---
+>                     Episode 6: Scope and Subroutines
 346c346
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_7.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_7.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 7: Operators and Precedence</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 7: Operators and Precedence
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_7.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_7.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 7: Operators and Precedence
+---
+>                     Episode 7: Operators and Precedence
 177c177
-< <p>Note that some operators are missing. See the exercises section for this. For more details on the use of the optable, check out <em>docs/pct/pct_optable_guide.pod</em> in the Parrot repository.</p>
----
-> <p>Note that some operators are missing. See the exercises section for this. For more details on the use of the optable, check out <em><a href="../../../../docs/pct/pct_optable_guide.pod.html">docs/pct/pct_optable_guide.pod</a></em> in the Parrot repository.</p>
+< <p>Note that some operators are missing. See the exercises section for this. For more details on the use of the optable, check out <em><a href="../../../../docs/pct/pct_optable_guide.pod.html">docs/pct/pct_optable_guide.pod</a></em> in the Parrot repository.</p>
+---
+> <p>Note that some operators are missing. See the exercises section for this. For more details on the use of the optable, check out <em>docs/pct/pct_optable_guide.pod</em> in the Parrot repository.</p>
 341c341
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_8.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_8.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 8: Hashtables and Arrays</title>
-23c23
-<                     Untitled
----
->                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 8: Hashtables and Arrays
+<               Copyright &copy; 2002-2009, Parrot Foundation.
+---
+>               Copyright &copy; 2002-2010, Parrot Foundation.
+diff -r parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_8.pod.html parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_8.pod.html
+23c23
+<                     <a href="../../../../../html/index.html">Home</a> &raquo; <a href="../../../../../html/PCT_Tutorial.html">PCT Tutorial</a> &raquo; Episode 8: Hashtables and Arrays
+---
+>                     Episode 8: Hashtables and Arrays
 333c333
-<               Copyright &copy; 2002-2010, Parrot Foundation.
----
->               Copyright &copy; 2002-2009, Parrot Foundation.
-diff -r parrot/docs/html/examples/languages/squaak/doc/tutorial_episode_9.pod.html parrot-trunk/docs/html/examples/languages/squaak/doc/tutorial_episode_9.pod.html
-5c5
-<         <title>Parrot  - Untitled</title>
----
->         <title>Parrot  - Episode 9: Wrap up and Conclusion</title>
-23c23