Context Navigation

Changes between Version 2 and Version 3 of CleanupMakeHtml

Timestamp:: 07/18/10 20:24:55 (12 years ago)
Author:: coke
Comment:: Track resources URL...

Legend:

: Unmodified
: Added
: Removed
: Modified

CleanupMakeHtml

v2	v3
11	11	Only in parrot-trunk/docs/html: developer.html
12	12	Only in parrot-trunk/docs/html/docs/book/pct: ch01_introduction.pod.html
13		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
14		5c5
15		< <title>Parrot - Getting Started</title>
16		---
17		> <title>Parrot - Untitled</title>
18		7c7
19		< href="../../../../resources/parrot.css"
20		---
21		> href="/parrot.css"
22		17c17
23		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
24		---
25		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
26		23c23
27		< <a href="../../../../html/index.html">Home</a> » Getting Started
28		---
29		> Untitled
30		150a151,169
	13	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
	14	5c5
	15	< <title>Parrot - Untitled</title>
	16	---
	17	> <title>Parrot - Getting Started</title>
	18	23c23
	19	< Untitled
	20	---
	21	> <a href="../../../../html/index.html">Home</a> » Getting Started
	22	151,169d150
	23	<
	24	< <h1><a name="POD_ERRORS"
	25	< >POD ERRORS</a></h1>
	26	<
	27	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	28	<
	29	< <dl>
	30	< <dt><a name="Around_line_9:"
	31	< >Around line 9:</a></dt>
	32	< Deleting unknown formatting code U<>Deleting unknown formatting code U<>
	33	< <dt><a name="Around_line_16:"
	34	< >Around line 16:</a></dt>
	35	< Deleting unknown formatting code U<>
	36	< <dt><a name="Around_line_120:"
	37	< >Around line 120:</a></dt>
	38	< =end for without matching =begin. (Stack: =over)
	39	< <dt><a name="Around_line_131:"
	40	< >Around line 131:</a></dt>
	41	< =end for without matching =begin. (Stack: =over)</dl>
	42	173c154
	43	< Copyright © 2002-2010, Parrot Foundation.
	44	---
	45	> Copyright © 2002-2009, Parrot Foundation.
	46	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
	47	5c5
	48	< <title>Parrot - Untitled</title>
	49	---
	50	> <title>Parrot - Parrot Compiler Tools</title>
	51	23c23
	52	< Untitled
	53	---
	54	> <a href="../../../../html/index.html">Home</a> » Parrot Compiler Tools
	55	339,357d338
	56	<
	57	< <h1><a name="POD_ERRORS"
	58	< >POD ERRORS</a></h1>
	59	<
	60	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	61	<
	62	< <dl>
	63	< <dt><a name="Around_line_5:"
	64	< >Around line 5:</a></dt>
	65	< A non-empty Z<>
	66	< <dt><a name="Around_line_44:"
	67	< >Around line 44:</a></dt>
	68	< Deleting unknown formatting code N<>
	69	< <dt><a name="Around_line_70:"
	70	< >Around line 70:</a></dt>
	71	< Deleting unknown formatting code N<>
	72	< <dt><a name="Around_line_177:"
	73	< >Around line 177:</a></dt>
	74	< Deleting unknown formatting code N<></dl>
	75	361c342
	76	< Copyright © 2002-2010, Parrot Foundation.
	77	---
	78	> Copyright © 2002-2009, Parrot Foundation.
	79	diff -r parrot/docs/html/docs/book/pct/ch04_pge.pod.html parrot-trunk/docs/html/docs/book/pct/ch04_pge.pod.html
	80	5c5
	81	< <title>Parrot - Untitled</title>
	82	---
	83	> <title>Parrot - Grammar Engine</title>
	84	23c23
	85	< Untitled
	86	---
	87	> <a href="../../../../html/index.html">Home</a> » Grammar Engine
	88	628,724d627
	89	<
	90	< <h1><a name="POD_ERRORS"
	91	< >POD ERRORS</a></h1>
	92	<
	93	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	94	<
	95	< <dl>
	96	< <dt><a name="Around_line_32:"
	97	< >Around line 32:</a></dt>
	98	< Deleting unknown formatting code N<>
	99	< <dt><a name="Around_line_117:"
	100	< >Around line 117:</a></dt>
	101	< =end for without matching =begin. (Stack: [empty])
	102	< <dt><a name="Around_line_318:"
	103	< >Around line 318:</a></dt>
	104	< A non-empty Z<>
	105	< <dt><a name="Around_line_339:"
	106	< >Around line 339:</a></dt>
	107	< Deleting unknown formatting code A<>
	108	< <dt><a name="Around_line_541:"
	109	< >Around line 541:</a></dt>
	110	< A non-empty Z<>
	111	< <dt><a name="Around_line_546:"
	112	< >Around line 546:</a></dt>
	113	< Deleting unknown formatting code R<>
	114	< <dt><a name="Around_line_560:"
	115	< >Around line 560:</a></dt>
	116	< Deleting unknown formatting code A<>
	117	< <dt><a name="Around_line_631:"
	118	< >Around line 631:</a></dt>
	119	< A non-empty Z<>
	120	< <dt><a name="Around_line_653:"
	121	< >Around line 653:</a></dt>
	122	< Deleting unknown formatting code N<>
	123	< <dt><a name="Around_line_675:"
	124	< >Around line 675:</a></dt>
	125	< Deleting unknown formatting code A<>
	126	< <dt><a name="Around_line_780:"
	127	< >Around line 780:</a></dt>
	128	< A non-empty Z<>
	129	< <dt><a name="Around_line_805:"
	130	< >Around line 805:</a></dt>
	131	< Deleting unknown formatting code R<>Deleting unknown formatting code R<>
	132	< <dt><a name="Around_line_809:"
	133	< >Around line 809:</a></dt>
	134	< Deleting unknown formatting code R<>Deleting unknown formatting code R<>
	135	< <dt><a name="Around_line_820:"
	136	< >Around line 820:</a></dt>
	137	< Deleting unknown formatting code R<>Deleting unknown formatting code R<>Deleting unknown formatting code R<>Deleting unknown formatting code R<>Deleting unknown formatting code R<>
	138	< <dt><a name="Around_line_836:"
	139	< >Around line 836:</a></dt>
	140	< Deleting unknown formatting code A<>
	141	< <dt><a name="Around_line_981:"
	142	< >Around line 981:</a></dt>
	143	< A non-empty Z<>
	144	< <dt><a name="Around_line_983:"
	145	< >Around line 983:</a></dt>
	146	< Deleting unknown formatting code A<>
	147	< <dt><a name="Around_line_1076:"
	148	< >Around line 1076:</a></dt>
	149	< A non-empty Z<>
	150	< <dt><a name="Around_line_1078:"
	151	< >Around line 1078:</a></dt>
	152	< Deleting unknown formatting code A<>
	153	< <dt><a name="Around_line_1090:"
	154	< >Around line 1090:</a></dt>
	155	< =end for without matching =begin. (Stack: [empty])
	156	< <dt><a name="Around_line_1150:"
	157	< >Around line 1150:</a></dt>
	158	< Deleting unknown formatting code N<>
	159	< <dt><a name="Around_line_1159:"
	160	< >Around line 1159:</a></dt>
	161	< =end for without matching =begin. (Stack: [empty])
	162	< <dt><a name="Around_line_1194:"
	163	< >Around line 1194:</a></dt>
	164	< Deleting unknown formatting code N<>
	165	< <dt><a name="Around_line_1303:"
	166	< >Around line 1303:</a></dt>
	167	< =end for without matching =begin. (Stack: [empty])
	168	< <dt><a name="Around_line_1372:"
	169	< >Around line 1372:</a></dt>
	170	< =end for without matching =begin. (Stack: [empty])
	171	< <dt><a name="Around_line_1428:"
	172	< >Around line 1428:</a></dt>
	173	< A non-empty Z<>
	174	< <dt><a name="Around_line_1477:"
	175	< >Around line 1477:</a></dt>
	176	< =end for without matching =begin. (Stack: [empty])
	177	< <dt><a name="Around_line_1496:"
	178	< >Around line 1496:</a></dt>
	179	< Deleting unknown formatting code N<>
	180	< <dt><a name="Around_line_1502:"
	181	< >Around line 1502:</a></dt>
	182	< Deleting unknown formatting code N<>
	183	< <dt><a name="Around_line_1513:"
	184	< >Around line 1513:</a></dt>
	185	< =end for without matching =begin. (Stack: [empty])</dl>
	186	728c631
	187	< Copyright © 2002-2010, Parrot Foundation.
	188	---
	189	> Copyright © 2002-2009, Parrot Foundation.
	190	diff -r parrot/docs/html/docs/book/pct/ch05_nqp.pod.html parrot-trunk/docs/html/docs/book/pct/ch05_nqp.pod.html
	191	5c5
	192	< <title>Parrot - Untitled</title>
	193	---
	194	> <title>Parrot - Grammar Actions</title>
	195	23c23
	196	< Untitled
	197	---
	198	> <a href="../../../../html/index.html">Home</a> » Grammar Actions
	199	223,238d222
	200	<
	201	< <h1><a name="POD_ERRORS"
	202	< >POD ERRORS</a></h1>
	203	<
	204	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	205	<
	206	< <dl>
	207	< <dt><a name="Around_line_29:"
	208	< >Around line 29:</a></dt>
	209	< Deleting unknown formatting code N<>
	210	< <dt><a name="Around_line_106:"
	211	< >Around line 106:</a></dt>
	212	< =end for without matching =begin. (Stack: [empty])
	213	< <dt><a name="Around_line_190:"
	214	< >Around line 190:</a></dt>
	215	< =end for without matching =begin. (Stack: [empty])</dl>
	216	242c226
	217	< Copyright © 2002-2010, Parrot Foundation.
	218	---
	219	> Copyright © 2002-2009, Parrot Foundation.
	220	diff -r parrot/docs/html/docs/book/pir/ch01_introduction.pod.html parrot-trunk/docs/html/docs/book/pir/ch01_introduction.pod.html
	221	5c5
	222	< <title>Parrot - Untitled</title>
	223	---
	224	> <title>Parrot - Introduction</title>
	225	23c23
	226	< Untitled
	227	---
	228	> <a href="../../../../html/index.html">Home</a> » Introduction
	229	159,188d158
	230	<
	231	< <h1><a name="POD_ERRORS"
	232	< >POD ERRORS</a></h1>
	233	<
	234	< <p>Hey!
	235	< <b>The above document had some coding errors,
	236	< which are explained below:</b></p>
	237	<
	238	< <dl>
	239	< <dt><a name="Around_line_12:"
	240	< >Around line 12:</a></dt>
	241	< Deleting unknown formatting code U<>
	242	< <dt><a name="Around_line_29:"
	243	< >Around line 29:</a></dt>
	244	< Deleting unknown formatting code U<>
	245	< <dt><a name="Around_line_39:"
	246	< >Around line 39:</a></dt>
	247	< Deleting unknown formatting code U<>
	248	< <dt><a name="Around_line_50:"
	249	< >Around line 50:</a></dt>
	250	< Deleting unknown formatting code N<>Deleting unknown formatting code U<>
	251	< <dt><a name="Around_line_57:"
	252	< >Around line 57:</a></dt>
	253	< Deleting unknown formatting code U<>Deleting unknown formatting code U<>
	254	< <dt><a name="Around_line_66:"
	255	< >Around line 66:</a></dt>
	256	< Deleting unknown formatting code U<>
	257	< <dt><a name="Around_line_75:"
	258	< >Around line 75:</a></dt>
	259	< Deleting unknown formatting code U<></dl>
	260	192c162
	261	< Copyright © 2002-2010, Parrot Foundation.
	262	---
	263	> Copyright © 2002-2009, Parrot Foundation.
	264	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
	265	5c5
	266	< <title>Parrot - Untitled</title>
	267	---
	268	> <title>Parrot - Getting Started</title>
	269	23c23
	270	< Untitled
	271	---
	272	> <a href="../../../../html/index.html">Home</a> » Getting Started
	273	60c60
	274	< <p>To install Parrot in a different location, use the <code>--prefix</code> option to <em>Configure.pl</em>:</p>
	275	---
	276	> <p>To install Parrot in a different location, use the <code>--prefix</code> option to <em><a href="../../../Configure.pl.html">Configure.pl</a></em>:</p>
	277	84,96d83
	278	<
	279	< <h1><a name="POD_ERRORS"
	280	< >POD ERRORS</a></h1>
	281	<
	282	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	283	<
	284	< <dl>
	285	< <dt><a name="Around_line_5:"
	286	< >Around line 5:</a></dt>
	287	< Deleting unknown formatting code N<>Deleting unknown formatting code U<>Deleting unknown formatting code N<>Deleting unknown formatting code U<>Deleting unknown formatting code U<>
	288	< <dt><a name="Around_line_48:"
	289	< >Around line 48:</a></dt>
	290	< Deleting unknown formatting code N<></dl>
	291	100c87
	292	< Copyright © 2002-2010, Parrot Foundation.
	293	---
	294	> Copyright © 2002-2009, Parrot Foundation.
	295	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
	296	5c5
	297	< <title>Parrot - Untitled</title>
	298	---
	299	> <title>Parrot - Basic Syntax</title>
	300	23c23
	301	< Untitled
	302	---
	303	> <a href="../../../../html/index.html">Home</a> » Basic Syntax
	304	213,231d212
	305	<
	306	< <h1><a name="POD_ERRORS"
	307	< >POD ERRORS</a></h1>
	308	<
	309	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	310	<
	311	< <dl>
	312	< <dt><a name="Around_line_5:"
	313	< >Around line 5:</a></dt>
	314	< A non-empty Z<>
	315	< <dt><a name="Around_line_62:"
	316	< >Around line 62:</a></dt>
	317	< A non-empty Z<>
	318	< <dt><a name="Around_line_143:"
	319	< >Around line 143:</a></dt>
	320	< Deleting unknown formatting code N<>
	321	< <dt><a name="Around_line_243:"
	322	< >Around line 243:</a></dt>
	323	< Deleting unknown formatting code N<>Deleting unknown formatting code N<></dl>
	324	235c216
	325	< Copyright © 2002-2010, Parrot Foundation.
	326	---
	327	> Copyright © 2002-2009, Parrot Foundation.
	328	diff -r parrot/docs/html/docs/book/pir/ch04_variables.pod.html parrot-trunk/docs/html/docs/book/pir/ch04_variables.pod.html
	329	5c5
	330	< <title>Parrot - Untitled</title>
	331	---
	332	> <title>Parrot - Variables</title>
	333	23c23
	334	< Untitled
	335	---
	336	> <a href="../../../../html/index.html">Home</a> » Variables
	337	279,284c279,291
	338	< Both C<and> and C<or> are short-circuiting ops. If they can determine what
	339	< value to return from the first argument, they'll never evaluate the second.
	340	< This is significant only for PMCs, as they might have side effects on
	341	< evaluation.The C<xor>X<xor opcode> opcode returns the first argument if it is the only
	342	< true value, returns the second argument if it is the only true value, and
	343	< returns false if both values are true or both are false:<pre> $I0 = xor 1, 0 # returns 1
	344	---
	345	> </pre>
	346	> <p>Both <code>and</code> and <code>or</code> are short-circuiting ops.
	347	> If they can determine what value to return from the first argument,
	348	> they'll never evaluate the second.
	349	> This is significant only for PMCs,
	350	> as they might have side effects on evaluation.</p>
31	351	>
32		> <h1><a name="POD_ERRORS"
33		> >POD ERRORS</a></h1>
34		>
35		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
36		>
37		> <dl>
38		> <dt><a name="Around_line_9:"
39		> >Around line 9:</a></dt>
40		> Deleting unknown formatting code U<>Deleting unknown formatting code U<>
41		> <dt><a name="Around_line_16:"
42		> >Around line 16:</a></dt>
43		> Deleting unknown formatting code U<>
44		> <dt><a name="Around_line_120:"
45		> >Around line 120:</a></dt>
46		> =end for without matching =begin. (Stack: =over)
47		> <dt><a name="Around_line_131:"
48		> >Around line 131:</a></dt>
49		> =end for without matching =begin. (Stack: =over)</dl>
50		154c173
51		< Copyright © 2002-2009, Parrot Foundation.
52		---
53		> Copyright © 2002-2010, Parrot Foundation.
54		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
55		5c5
56		< <title>Parrot - Parrot Compiler Tools</title>
57		---
58		> <title>Parrot - Untitled</title>
59		7c7
60		< href="../../../../resources/parrot.css"
61		---
62		> href="/parrot.css"
63		17c17
64		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
65		---
66		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
67		23c23
68		< <a href="../../../../html/index.html">Home</a> » Parrot Compiler Tools
69		---
70		> Untitled
71		338a339,357
72		>
73		> <h1><a name="POD_ERRORS"
74		> >POD ERRORS</a></h1>
75		>
76		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
77		>
78		> <dl>
79		> <dt><a name="Around_line_5:"
80		> >Around line 5:</a></dt>
81		> A non-empty Z<>
82		> <dt><a name="Around_line_44:"
83		> >Around line 44:</a></dt>
84		> Deleting unknown formatting code N<>
85		> <dt><a name="Around_line_70:"
86		> >Around line 70:</a></dt>
87		> Deleting unknown formatting code N<>
88		> <dt><a name="Around_line_177:"
89		> >Around line 177:</a></dt>
90		> Deleting unknown formatting code N<></dl>
91		342c361
92		< Copyright © 2002-2009, Parrot Foundation.
93		---
94		> Copyright © 2002-2010, Parrot Foundation.
95		diff -r parrot-trunk/docs/html/docs/book/pct/ch04_pge.pod.html parrot/docs/html/docs/book/pct/ch04_pge.pod.html
96		5c5
97		< <title>Parrot - Grammar Engine</title>
98		---
99		> <title>Parrot - Untitled</title>
100		7c7
101		< href="../../../../resources/parrot.css"
102		---
103		> href="/parrot.css"
104		17c17
105		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
106		---
107		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
108		23c23
109		< <a href="../../../../html/index.html">Home</a> » Grammar Engine
110		---
111		> Untitled
112		627a628,724
113		>
114		> <h1><a name="POD_ERRORS"
115		> >POD ERRORS</a></h1>
116		>
117		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
118		>
119		> <dl>
120		> <dt><a name="Around_line_32:"
121		> >Around line 32:</a></dt>
122		> Deleting unknown formatting code N<>
123		> <dt><a name="Around_line_117:"
124		> >Around line 117:</a></dt>
125		> =end for without matching =begin. (Stack: [empty])
126		> <dt><a name="Around_line_318:"
127		> >Around line 318:</a></dt>
128		> A non-empty Z<>
129		> <dt><a name="Around_line_339:"
130		> >Around line 339:</a></dt>
131		> Deleting unknown formatting code A<>
132		> <dt><a name="Around_line_541:"
133		> >Around line 541:</a></dt>
134		> A non-empty Z<>
135		> <dt><a name="Around_line_546:"
136		> >Around line 546:</a></dt>
137		> Deleting unknown formatting code R<>
138		> <dt><a name="Around_line_560:"
139		> >Around line 560:</a></dt>
140		> Deleting unknown formatting code A<>
141		> <dt><a name="Around_line_631:"
142		> >Around line 631:</a></dt>
143		> A non-empty Z<>
144		> <dt><a name="Around_line_653:"
145		> >Around line 653:</a></dt>
146		> Deleting unknown formatting code N<>
147		> <dt><a name="Around_line_675:"
148		> >Around line 675:</a></dt>
149		> Deleting unknown formatting code A<>
150		> <dt><a name="Around_line_780:"
151		> >Around line 780:</a></dt>
152		> A non-empty Z<>
153		> <dt><a name="Around_line_805:"
154		> >Around line 805:</a></dt>
155		> Deleting unknown formatting code R<>Deleting unknown formatting code R<>
156		> <dt><a name="Around_line_809:"
157		> >Around line 809:</a></dt>
158		> Deleting unknown formatting code R<>Deleting unknown formatting code R<>
159		> <dt><a name="Around_line_820:"
160		> >Around line 820:</a></dt>
161		> Deleting unknown formatting code R<>Deleting unknown formatting code R<>Deleting unknown formatting code R<>Deleting unknown formatting code R<>Deleting unknown formatting code R<>
162		> <dt><a name="Around_line_836:"
163		> >Around line 836:</a></dt>
164		> Deleting unknown formatting code A<>
165		> <dt><a name="Around_line_981:"
166		> >Around line 981:</a></dt>
167		> A non-empty Z<>
168		> <dt><a name="Around_line_983:"
169		> >Around line 983:</a></dt>
170		> Deleting unknown formatting code A<>
171		> <dt><a name="Around_line_1076:"
172		> >Around line 1076:</a></dt>
173		> A non-empty Z<>
174		> <dt><a name="Around_line_1078:"
175		> >Around line 1078:</a></dt>
176		> Deleting unknown formatting code A<>
177		> <dt><a name="Around_line_1090:"
178		> >Around line 1090:</a></dt>
179		> =end for without matching =begin. (Stack: [empty])
180		> <dt><a name="Around_line_1150:"
181		> >Around line 1150:</a></dt>
182		> Deleting unknown formatting code N<>
183		> <dt><a name="Around_line_1159:"
184		> >Around line 1159:</a></dt>
185		> =end for without matching =begin. (Stack: [empty])
186		> <dt><a name="Around_line_1194:"
187		> >Around line 1194:</a></dt>
188		> Deleting unknown formatting code N<>
189		> <dt><a name="Around_line_1303:"
190		> >Around line 1303:</a></dt>
191		> =end for without matching =begin. (Stack: [empty])
192		> <dt><a name="Around_line_1372:"
193		> >Around line 1372:</a></dt>
194		> =end for without matching =begin. (Stack: [empty])
195		> <dt><a name="Around_line_1428:"
196		> >Around line 1428:</a></dt>
197		> A non-empty Z<>
198		> <dt><a name="Around_line_1477:"
199		> >Around line 1477:</a></dt>
200		> =end for without matching =begin. (Stack: [empty])
201		> <dt><a name="Around_line_1496:"
202		> >Around line 1496:</a></dt>
203		> Deleting unknown formatting code N<>
204		> <dt><a name="Around_line_1502:"
205		> >Around line 1502:</a></dt>
206		> Deleting unknown formatting code N<>
207		> <dt><a name="Around_line_1513:"
208		> >Around line 1513:</a></dt>
209		> =end for without matching =begin. (Stack: [empty])</dl>
210		631c728
211		< Copyright © 2002-2009, Parrot Foundation.
212		---
213		> Copyright © 2002-2010, Parrot Foundation.
214		diff -r parrot-trunk/docs/html/docs/book/pct/ch05_nqp.pod.html parrot/docs/html/docs/book/pct/ch05_nqp.pod.html
215		5c5
216		< <title>Parrot - Grammar Actions</title>
217		---
218		> <title>Parrot - Untitled</title>
219		7c7
220		< href="../../../../resources/parrot.css"
221		---
222		> href="/parrot.css"
223		17c17
224		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
225		---
226		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
227		23c23
228		< <a href="../../../../html/index.html">Home</a> » Grammar Actions
229		---
230		> Untitled
231		222a223,238
232		>
233		> <h1><a name="POD_ERRORS"
234		> >POD ERRORS</a></h1>
235		>
236		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
237		>
238		> <dl>
239		> <dt><a name="Around_line_29:"
240		> >Around line 29:</a></dt>
241		> Deleting unknown formatting code N<>
242		> <dt><a name="Around_line_106:"
243		> >Around line 106:</a></dt>
244		> =end for without matching =begin. (Stack: [empty])
245		> <dt><a name="Around_line_190:"
246		> >Around line 190:</a></dt>
247		> =end for without matching =begin. (Stack: [empty])</dl>
248		226c242
249		< Copyright © 2002-2009, Parrot Foundation.
250		---
251		> Copyright © 2002-2010, Parrot Foundation.
252		diff -r parrot-trunk/docs/html/docs/book/pir/ch01_introduction.pod.html parrot/docs/html/docs/book/pir/ch01_introduction.pod.html
253		5c5
254		< <title>Parrot - Introduction</title>
255		---
256		> <title>Parrot - Untitled</title>
257		7c7
258		< href="../../../../resources/parrot.css"
259		---
260		> href="/parrot.css"
261		17c17
262		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
263		---
264		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
265		23c23
266		< <a href="../../../../html/index.html">Home</a> » Introduction
267		---
268		> Untitled
269		158a159,188
270		>
271		> <h1><a name="POD_ERRORS"
272		> >POD ERRORS</a></h1>
273		>
274		> <p>Hey!
275		> <b>The above document had some coding errors,
276		> which are explained below:</b></p>
277		>
278		> <dl>
279		> <dt><a name="Around_line_12:"
280		> >Around line 12:</a></dt>
281		> Deleting unknown formatting code U<>
282		> <dt><a name="Around_line_29:"
283		> >Around line 29:</a></dt>
284		> Deleting unknown formatting code U<>
285		> <dt><a name="Around_line_39:"
286		> >Around line 39:</a></dt>
287		> Deleting unknown formatting code U<>
288		> <dt><a name="Around_line_50:"
289		> >Around line 50:</a></dt>
290		> Deleting unknown formatting code N<>Deleting unknown formatting code U<>
291		> <dt><a name="Around_line_57:"
292		> >Around line 57:</a></dt>
293		> Deleting unknown formatting code U<>Deleting unknown formatting code U<>
294		> <dt><a name="Around_line_66:"
295		> >Around line 66:</a></dt>
296		> Deleting unknown formatting code U<>
297		> <dt><a name="Around_line_75:"
298		> >Around line 75:</a></dt>
299		> Deleting unknown formatting code U<></dl>
300		162c192
301		< Copyright © 2002-2009, Parrot Foundation.
302		---
303		> Copyright © 2002-2010, Parrot Foundation.
304		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
305		5c5
306		< <title>Parrot - Getting Started</title>
307		---
308		> <title>Parrot - Untitled</title>
309		7c7
310		< href="../../../../resources/parrot.css"
311		---
312		> href="/parrot.css"
313		17c17
314		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
315		---
316		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
317		23c23
318		< <a href="../../../../html/index.html">Home</a> » Getting Started
319		---
320		> Untitled
321		60c60
322		< <p>To install Parrot in a different location, use the <code>--prefix</code> option to <em><a href="../../../Configure.pl.html">Configure.pl</a></em>:</p>
323		---
324		> <p>To install Parrot in a different location, use the <code>--prefix</code> option to <em>Configure.pl</em>:</p>
325		83a84,96
326		>
327		> <h1><a name="POD_ERRORS"
328		> >POD ERRORS</a></h1>
329		>
330		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
331		>
332		> <dl>
333		> <dt><a name="Around_line_5:"
334		> >Around line 5:</a></dt>
335		> Deleting unknown formatting code N<>Deleting unknown formatting code U<>Deleting unknown formatting code N<>Deleting unknown formatting code U<>Deleting unknown formatting code U<>
336		> <dt><a name="Around_line_48:"
337		> >Around line 48:</a></dt>
338		> Deleting unknown formatting code N<></dl>
339		87c100
340		< Copyright © 2002-2009, Parrot Foundation.
341		---
342		> Copyright © 2002-2010, Parrot Foundation.
343		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
344		5c5
345		< <title>Parrot - Basic Syntax</title>
346		---
347		> <title>Parrot - Untitled</title>
348		7c7
349		< href="../../../../resources/parrot.css"
350		---
351		> href="/parrot.css"
352		17c17
353		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
354		---
355		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
356		23c23
357		< <a href="../../../../html/index.html">Home</a> » Basic Syntax
358		---
359		> Untitled
360		212a213,231
361		>
362		> <h1><a name="POD_ERRORS"
363		> >POD ERRORS</a></h1>
364		>
365		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
366		>
367		> <dl>
368		> <dt><a name="Around_line_5:"
369		> >Around line 5:</a></dt>
370		> A non-empty Z<>
371		> <dt><a name="Around_line_62:"
372		> >Around line 62:</a></dt>
373		> A non-empty Z<>
374		> <dt><a name="Around_line_143:"
375		> >Around line 143:</a></dt>
376		> Deleting unknown formatting code N<>
377		> <dt><a name="Around_line_243:"
378		> >Around line 243:</a></dt>
379		> Deleting unknown formatting code N<>Deleting unknown formatting code N<></dl>
380		216c235
381		< Copyright © 2002-2009, Parrot Foundation.
382		---
383		> Copyright © 2002-2010, Parrot Foundation.
384		diff -r parrot-trunk/docs/html/docs/book/pir/ch04_variables.pod.html parrot/docs/html/docs/book/pir/ch04_variables.pod.html
385		5c5
386		< <title>Parrot - Variables</title>
387		---
388		> <title>Parrot - Untitled</title>
389		7c7
390		< href="../../../../resources/parrot.css"
391		---
392		> href="/parrot.css"
393		17c17
394		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
395		---
396		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
397		23c23
398		< <a href="../../../../html/index.html">Home</a> » Variables
399		---
400		> Untitled
401		279,291c279,284
402		< </pre>
403		< <p>Both <code>and</code> and <code>or</code> are short-circuiting ops.
404		< If they can determine what value to return from the first argument,
405		< they'll never evaluate the second.
406		< This is significant only for PMCs,
407		< as they might have side effects on evaluation.</p>
408		<
409		< <p>The <code>xor</code><!--
410		< INDEX: xor opcode
411		< --> opcode returns the first argument if it is the only true value,
412		< returns the second argument if it is the only true value,
413		< and returns false if both values are true or both are false:</p>
414		< <pre> $I0 = xor 1, 0 # returns 1
415		---
416		> Both C<and> and C<or> are short-circuiting ops. If they can determine what
417		> value to return from the first argument, they'll never evaluate the second.
418		> This is significant only for PMCs, as they might have side effects on
419		> evaluation.The C<xor>X<xor opcode> opcode returns the first argument if it is the only
420		> true value, returns the second argument if it is the only true value, and
421		> returns false if both values are true or both are false:<pre> $I0 = xor 1, 0 # returns 1
422		296,298c289,290
423		< <p>The <code>not</code><!--
424		< INDEX: not opcode
425		< --> opcode returns a true value when the argument is false and a false value if the argument is true:</p>
426		---
427		> The C<not>X<not opcode> opcode returns a true value when the argument is false
428		> and a false value if the argument is true:
429		302,316c294,298
430		< <p><!--
431		< INDEX: bitwise opcodes
432		< --> The bitwise opcodes operate on their values a single bit at a time.
433		< <code>band</code><!--
434		< INDEX: band opcode
435		< -->,
436		< <code>bor</code><!--
437		< INDEX: bor opcode
438		< -->,
439		< and <code>bxor</code><!--
440		< INDEX: bxor opcode
441		< --> return a value that is the logical AND,
442		< OR,
443		< or XOR of each bit in the source arguments.
444		< They each take two arguments.</p>
445		---
446		> X<bitwise opcodes>
447		> The bitwise opcodes operate on their values a single bit at a time.
448		> C<band>X<band opcode>, C<bor>X<bor opcode>, and C<bxor>X<bxor opcode> return a
449		> value that is the logical AND, OR, or XOR of each bit in the source arguments.
450		> They each take two arguments.
451		324,326c306,307
452		< <p><code>band</code>,
453		< <code>bor</code>,
454		< and <code>bxor</code> also have variants that modify the result in place.</p>
455		---
456		> C<band>, C<bor>, and C<bxor> also have variants that modify the result
457		> in place.
458		334,336c315
459		< <p><code>bnot</code><!--
460		< INDEX: bnot opcode
461		< --> is the logical NOT of each bit in the source argument.</p>
462		---
463		> C<bnot>X<bnot opcode> is the logical NOT of each bit in the source argument.
464		343,349c322,326
465		< <p><!--
466		< INDEX: shl opcode
467		< --> <!--
468		< INDEX: shr opcode
469		< --> <!--
470		< INDEX: lsr opcode
471		< --> The logical and arithmetic shift operations shift their values by a specified number of bits:</p>
472		---
473		> X<shl opcode>
474		> X<shr opcode>
475		> X<lsr opcode>
476		> The logical and arithmetic shift operations shift their values by a specified
477		> number of bits:
478		361,372c338,344
479		< <p><!--
480		< INDEX: strings
481		< --> Parrot strings are buffers of variable-sized data.
482		< The most common use of strings is to store text data.
483		< Strings can also hold binary or other non-textual data,
484		< though this is rare.In general,
485		< a custom PMC is more useful. Parrot strings are flexible and powerful,
486		< to handle the complexity of human-readable (and computer-representable) text data.
487		< String operations work with string literals,
488		< variables,
489		< and constants,
490		< and with string-like PMCs.</p>
491		---
492		> X<strings>
493		> Parrot strings are buffers of variable-sized data. The most common use of
494		> strings is to store text data. Strings can also hold binary or other
495		> non-textual data, though this is rare.N<In general, a custom PMC is more
496		> useful.> Parrot strings are flexible and powerful, to handle the complexity of
497		> human-readable (and computer-representable) text data. String operations work
498		> with string literals, variables, and constants, and with string-like PMCs.
499		377,381c349,353
500		< <p><!--
501		< INDEX: string escapes
502		< --> <!--
503		< INDEX: escape sequences
504		< --></p>
505		---
506		> X<string escapes>
507		> X<escape sequences>
508		>
509		> Strings in double-quotes allow escape sequences using backslashes. Strings in
510		> single-quotes only allow escapes for nested quotes:
511		383,384c355,356
512		< <p>Strings in double-quotes allow escape sequences using backslashes.
513		< Strings in single-quotes only allow escapes for nested quotes:</p>
514		---
515		> $S0 = "This string is \n on two lines"
516		> $S0 = 'This is a \n one-line string with a slash in it'
517		386,387d357
518		< <pre> $S0 = "This string is \n on two lines"
519		< $S0 = 'This is a \n one-line string with a slash in it'</pre>
520		389c359,360
521		< <p>Table 4.1 shows the escape sequences Parrot supports in double-quoted strings.</p>
522		---
523		> Table 4.1 shows the escape sequences Parrot supports in double-quoted
524		> strings.
525		394,396c365,375
526		< <p><!--
527		< INDEX: heredocs
528		< --> If you need more flexibility in defining a string, use a heredoc string literal. The <code><<</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>
529		---
530		> X<heredocs>
531		> If you need more flexibility in defining a string, use a heredoc string
532		> literal. The C<E<lt>E<lt>> operator starts a heredoc. The string terminator
533		> immediately follows. All text until the terminator is part of the string. The
534		> terminator must appear on its own line, must appear at the beginning of the
535		> line, and may not have any trailing whitespace.
536		>
537		> $S2 = <<"End_Token"
538		> This is a multi-line string literal. Notice that
539		> it doesn't use quotation marks.
540		> End_Token
541		398,401d376
542		< <pre> $S2 = <<"End_Token"
	352	> <p>The <code>xor</code><!--
	353	> INDEX: xor opcode
	354	> --> opcode returns the first argument if it is the only true value,
	355	> returns the second argument if it is the only true value,
	356	> and returns false if both values are true or both are false:</p>
	357	> <pre> $I0 = xor 1, 0 # returns 1
	358	289,290c296,298
	359	< The C<not>X<not opcode> opcode returns a true value when the argument is false
	360	< and a false value if the argument is true:
	361	---
	362	> <p>The <code>not</code><!--
	363	> INDEX: not opcode
	364	> --> opcode returns a true value when the argument is false and a false value if the argument is true:</p>
	365	294,298c302,316
	366	< X<bitwise opcodes>
	367	< The bitwise opcodes operate on their values a single bit at a time.
	368	< C<band>X<band opcode>, C<bor>X<bor opcode>, and C<bxor>X<bxor opcode> return a
	369	< value that is the logical AND, OR, or XOR of each bit in the source arguments.
	370	< They each take two arguments.
	371	---
	372	> <p><!--
	373	> INDEX: bitwise opcodes
	374	> --> The bitwise opcodes operate on their values a single bit at a time.
	375	> <code>band</code><!--
	376	> INDEX: band opcode
	377	> -->,
	378	> <code>bor</code><!--
	379	> INDEX: bor opcode
	380	> -->,
	381	> and <code>bxor</code><!--
	382	> INDEX: bxor opcode
	383	> --> return a value that is the logical AND,
	384	> OR,
	385	> or XOR of each bit in the source arguments.
	386	> They each take two arguments.</p>
	387	306,307c324,326
	388	< C<band>, C<bor>, and C<bxor> also have variants that modify the result
	389	< in place.
	390	---
	391	> <p><code>band</code>,
	392	> <code>bor</code>,
	393	> and <code>bxor</code> also have variants that modify the result in place.</p>
	394	315c334,336
	395	< C<bnot>X<bnot opcode> is the logical NOT of each bit in the source argument.
	396	---
	397	> <p><code>bnot</code><!--
	398	> INDEX: bnot opcode
	399	> --> is the logical NOT of each bit in the source argument.</p>
	400	322,326c343,349
	401	< X<shl opcode>
	402	< X<shr opcode>
	403	< X<lsr opcode>
	404	< The logical and arithmetic shift operations shift their values by a specified
	405	< number of bits:
	406	---
	407	> <p><!--
	408	> INDEX: shl opcode
	409	> --> <!--
	410	> INDEX: shr opcode
	411	> --> <!--
	412	> INDEX: lsr opcode
	413	> --> The logical and arithmetic shift operations shift their values by a specified number of bits:</p>
	414	338,344c361,372
	415	< X<strings>
	416	< Parrot strings are buffers of variable-sized data. The most common use of
	417	< strings is to store text data. Strings can also hold binary or other
	418	< non-textual data, though this is rare.N<In general, a custom PMC is more
	419	< useful.> Parrot strings are flexible and powerful, to handle the complexity of
	420	< human-readable (and computer-representable) text data. String operations work
	421	< with string literals, variables, and constants, and with string-like PMCs.
	422	---
	423	> <p><!--
	424	> INDEX: strings
	425	> --> Parrot strings are buffers of variable-sized data.
	426	> The most common use of strings is to store text data.
	427	> Strings can also hold binary or other non-textual data,
	428	> though this is rare.In general,
	429	> a custom PMC is more useful. Parrot strings are flexible and powerful,
	430	> to handle the complexity of human-readable (and computer-representable) text data.
	431	> String operations work with string literals,
	432	> variables,
	433	> and constants,
	434	> and with string-like PMCs.</p>
	435	349,353c377,381
	436	< X<string escapes>
	437	< X<escape sequences>
	438	<
	439	< Strings in double-quotes allow escape sequences using backslashes. Strings in
	440	< single-quotes only allow escapes for nested quotes:
	441	---
	442	> <p><!--
	443	> INDEX: string escapes
	444	> --> <!--
	445	> INDEX: escape sequences
	446	> --></p>
	447	355,356c383,384
	448	< $S0 = "This string is \n on two lines"
	449	< $S0 = 'This is a \n one-line string with a slash in it'
	450	---
	451	> <p>Strings in double-quotes allow escape sequences using backslashes.
	452	> Strings in single-quotes only allow escapes for nested quotes:</p>
	453	357a386,387
	454	> <pre> $S0 = "This string is \n on two lines"
	455	> $S0 = 'This is a \n one-line string with a slash in it'</pre>
	456	359,360c389
	457	< Table 4.1 shows the escape sequences Parrot supports in double-quoted
	458	< strings.
	459	---
	460	> <p>Table 4.1 shows the escape sequences Parrot supports in double-quoted strings.</p>
	461	365,375c394,396
	462	< X<heredocs>
	463	< If you need more flexibility in defining a string, use a heredoc string
	464	< literal. The C<E<lt>E<lt>> operator starts a heredoc. The string terminator
	465	< immediately follows. All text until the terminator is part of the string. The
	466	< terminator must appear on its own line, must appear at the beginning of the
	467	< line, and may not have any trailing whitespace.
	468	<
	469	< $S2 = <<"End_Token"
543	470	< This is a multi-line string literal. Notice that
544	471	< it doesn't use quotation marks.
545		< End_Token</pre>
546		406,410c381,382
547		< <p><!--
548		< INDEX: . operator
549		< --> <!--
550		< INDEX: strings;concatenation
551		< --></p>
552		---
553		> X<. operator>
554		> X<strings;concatenation>
555		412c384,386
556		< <p>Use the <code>.</code> operator to concatenate strings. The following example concatenates the string "cd" onto the string "ab" and stores the result in <code>$S1</code>.</p>
557		---
558		> Use the C<.> operator to concatenate strings. The following example
559		> concatenates the string "cd" onto the string "ab" and stores the result in
560		> C<$S1>.
561		417,419c391,394
562		< <p><!--
563		< INDEX: .= operator
564		< --> Concatenation has a <code>.=</code> variant to modify the result in place. In the next example, the <code>.=</code> operation appends "xy" onto the string "abcd" in <code>$S1</code>.</p>
565		---
566		> X<.= operator>
567		> Concatenation has a C<.=> variant to modify the result in place. In the
568		> next example, the C<.=> operation appends "xy" onto the string "abcd" in
569		> C<$S1>.
570		426,428c401,402
571		< <p><!--
572		< INDEX: repeat opcode
573		< --> The <code>repeat</code> opcode repeats a string a specified number of times:</p>
574		---
575		> X<repeat opcode>
576		> The C<repeat> opcode repeats a string a specified number of times:
577		433c407,408
578		< <p>In this example, <code>repeat</code> generates a new string with "a" repeated five times and stores it in <code>$S1</code>.</p>
579		---
580		> In this example, C<repeat> generates a new string with "a" repeated five
581		> times and stores it in C<$S1>.
582		438,440c413,415
583		< <p><!--
584		< INDEX: length opcode
585		< --> The <code>length</code> opcode returns the length of a string in characters. This won't be the same as the length in <i>bytes</i> for multibyte encoded strings:</p>
586		---
587		> X<length opcode>
588		> The C<length> opcode returns the length of a string in characters. This won't
589		> be the same as the length in I<bytes> for multibyte encoded strings:
590		445c420
591		< <p><code>length</code> has no equivalent for PMC strings.</p>
592		---
593		> C<length> has no equivalent for PMC strings.
594		450,452c425,428
595		< <p>The simplest version of the <code>substr</code><!--
596		< INDEX: substr opcode
597		< --> 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>
598		---
599		> The simplest version of the C<substr>X<substr opcode> opcode takes three
600		> arguments: a source string, an offset position, and a length. It returns a
601		> substring of the original string, starting from the offset position (0 is the
602		> first character) and spanning the length:
603		455,457c431,444
604		< <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 <code>$S0</code>.</p>
605		<
606		< <p>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.</p>
607		---
608		> This example extracts a two-character string from "abcde" at a one-character
609		> offset from the beginning of the string (starting with the second character).
610		> It generates a new string, "bc", in the destination register C<$S0>.
	472	< End_Token
	473	---
	474	> <p><!--
	475	> INDEX: heredocs
	476	> --> If you need more flexibility in defining a string, use a heredoc string literal. The <code><<</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>
	477	376a398,401
	478	> <pre> $S2 = <<"End_Token"
	479	> This is a multi-line string literal. Notice that
	480	> it doesn't use quotation marks.
	481	> End_Token</pre>
	482	381,382c406,410
	483	< X<. operator>
	484	< X<strings;concatenation>
	485	---
	486	> <p><!--
	487	> INDEX: . operator
	488	> --> <!--
	489	> INDEX: strings;concatenation
	490	> --></p>
	491	384,386c412
	492	< Use the C<.> operator to concatenate strings. The following example
	493	< concatenates the string "cd" onto the string "ab" and stores the result in
	494	< C<$S1>.
	495	---
	496	> <p>Use the <code>.</code> operator to concatenate strings. The following example concatenates the string "cd" onto the string "ab" and stores the result in <code>$S1</code>.</p>
	497	391,394c417,419
	498	< X<.= operator>
	499	< Concatenation has a C<.=> variant to modify the result in place. In the
	500	< next example, the C<.=> operation appends "xy" onto the string "abcd" in
	501	< C<$S1>.
	502	---
	503	> <p><!--
	504	> INDEX: .= operator
	505	> --> Concatenation has a <code>.=</code> variant to modify the result in place. In the next example, the <code>.=</code> operation appends "xy" onto the string "abcd" in <code>$S1</code>.</p>
	506	401,402c426,428
	507	< X<repeat opcode>
	508	< The C<repeat> opcode repeats a string a specified number of times:
	509	---
	510	> <p><!--
	511	> INDEX: repeat opcode
	512	> --> The <code>repeat</code> opcode repeats a string a specified number of times:</p>
	513	407,408c433
	514	< In this example, C<repeat> generates a new string with "a" repeated five
	515	< times and stores it in C<$S1>.
	516	---
	517	> <p>In this example, <code>repeat</code> generates a new string with "a" repeated five times and stores it in <code>$S1</code>.</p>
	518	413,415c438,440
	519	< X<length opcode>
	520	< The C<length> opcode returns the length of a string in characters. This won't
	521	< be the same as the length in I<bytes> for multibyte encoded strings:
	522	---
	523	> <p><!--
	524	> INDEX: length opcode
	525	> --> The <code>length</code> opcode returns the length of a string in characters. This won't be the same as the length in <i>bytes</i> for multibyte encoded strings:</p>
	526	420c445
	527	< C<length> has no equivalent for PMC strings.
	528	---
	529	> <p><code>length</code> has no equivalent for PMC strings.</p>
	530	425,428c450,452
	531	< The simplest version of the C<substr>X<substr opcode> opcode takes three
	532	< arguments: a source string, an offset position, and a length. It returns a
	533	< substring of the original string, starting from the offset position (0 is the
	534	< first character) and spanning the length:
	535	---
	536	> <p>The simplest version of the <code>substr</code><!--
	537	> INDEX: substr opcode
	538	> --> 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>
	539	431,444c455,457
	540	< This example extracts a two-character string from "abcde" at a one-character
	541	< offset from the beginning of the string (starting with the second character).
	542	< It generates a new string, "bc", in the destination register C<$S0>.
	543	<
	544	< When the offset position is negative, it counts backward from the end of the
	545	< string. Thus an offset of -1 starts at the last character of the string.
	546	<
	547	< C<substr> no longer has a four-argument form, as in-place string operations
	548	< have been removed. There is a C<replace> operator which will perform the
	549	< replacement and return a new_string without modifying the old_string.
	550	< The arguments are new_string, old_string, offset, count and
	551	< replacement_string. The old_string is copied to the new_string with the
	552	< replacement_string inserted from offset replacing the content for count
	553	< characters.
	554	---
	555	> <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 <code>$S0</code>.</p>
611	556	>
612		> When the offset position is negative, it counts backward from the end of the
613		> string. Thus an offset of -1 starts at the last character of the string.
	557	> <p>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.</p>
	558	446,447c459,461
	559	< This example replaces the substring "bc" in C<$S1> with the string "XYZ",
	560	< and returns "aXYZde" in C<$S0>, C<$S1> is not changed:
	561	---
	562	> <p><code>substr</code> no longer has a four-argument form, as in-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>
614	563	>
615		> C<substr> no longer has a four-argument form, as in-place string operations
616		> have been removed. There is a C<replace> operator which will perform the
617		> replacement and return a new_string without modifying the old_string.
618		> The arguments are new_string, old_string, offset, count and
619		> replacement_string. The old_string is copied to the new_string with the
620		> replacement_string inserted from offset replacing the content for count
621		> characters.
622		459,461c446,447
623		< <p><code>substr</code> no longer has a four-argument form, as in-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>
624		<
625		< <p>This example replaces the substring "bc" in <code>$S1</code> with the string "XYZ", and returns "aXYZde" in <code>$S0</code>, <code>$S1</code> is not changed:</p>
626		---
627		> This example replaces the substring "bc" in C<$S1> with the string "XYZ",
628		> and returns "aXYZde" in C<$S0>, C<$S1> is not changed:
629		467c453,456
630		< <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>
631		---
632		> When the offset position in a C<replace> is one character beyond the original
633		> string length, C<replace> appends the replacement string just like the
634		> concatenation operator. If the replacement string is an empty string, the
635		> opcode removes the characters from the original string in the new string.
636		475,479c464,469
637		< <p>The <code>chr</code><!--
638		< INDEX: chr opcode
639		< --> opcode takes an integer value and returns the corresponding character in the ASCII character set as a one-character string. The <code>ord</code><!--
640		< INDEX: ord opcode
641		< --> 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>
642		---
643		> The C<chr>X<chr opcode> opcode takes an integer value and returns the
644		> corresponding character in the ASCII character set as a one-character string.
645		> The C<ord>X<ord opcode> opcode takes a single character string and returns the
646		> integer value of the character at the first position in the string. The integer
647		> value of the character will differ depending on the current encoding of the
648		> string:
649		483c473,475
650		< <p><code>ord</code> 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>
651		---
652		> C<ord> has a two-argument variant that takes a character offset to select
653		> a single character from a multicharacter string. The offset must be within
654		> the length of the string:
655		486c478,479
656		< <p>A negative offset counts backward from the end of the string, so -1 is the last character.</p>
657		---
658		> A negative offset counts backward from the end of the string, so -1 is
659		> the last character.
660		492,494c485
661		< <p><!--
662		< INDEX: strings;formatting
663		< --></p>
664		---
665		> X<strings;formatting>
666		496,498c487,490
667		< <p>The <code>sprintf</code><!--
668		< INDEX: sprintf opcode
669		< --> 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>
670		---
671		> The C<sprintf>X<sprintf opcode> opcode generates a formatted string from a
672		> series of values. It takes two arguments: a string specifying the format, and
673		> an array PMC containing the values to be formatted. The format string and the
674		> result can be either strings or PMCs:
675		502,508c494,510
676		< <p>The format string is similar to C'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>
677		<
678		< <p>Each format field supports several specifier options: flags, width, precision, and size. Table 4.3 lists the format flags.</p>
679		<
680		< <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-point fields. If either width or precision is an asterisk (<code>*</code>), it takes its value from the next argument in the PMC.</p>
681		<
682		< <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>
683		---
684		> The format string is similar to C's C<sprintf> function with extensions for
685		> Parrot data types. Each format field in the string starts with a C<%> and ends
686		> with a character specifying the output format. Table 4.2 lists the available
687		> output format characters.
	564	> <p>This example replaces the substring "bc" in <code>$S1</code> with the string "XYZ", and returns "aXYZde" in <code>$S0</code>, <code>$S1</code> is not changed:</p>
	565	453,456c467
	566	< When the offset position in a C<replace> is one character beyond the original
	567	< string length, C<replace> appends the replacement string just like the
	568	< concatenation operator. If the replacement string is an empty string, the
	569	< opcode removes the characters from the original string in the new string.
	570	---
	571	> <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>
	572	464,469c475,479
	573	< The C<chr>X<chr opcode> opcode takes an integer value and returns the
	574	< corresponding character in the ASCII character set as a one-character string.
	575	< The C<ord>X<ord opcode> opcode takes a single character string and returns the
	576	< integer value of the character at the first position in the string. The integer
	577	< value of the character will differ depending on the current encoding of the
	578	< string:
	579	---
	580	> <p>The <code>chr</code><!--
	581	> INDEX: chr opcode
	582	> --> opcode takes an integer value and returns the corresponding character in the ASCII character set as a one-character string. The <code>ord</code><!--
	583	> INDEX: ord opcode
	584	> --> 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>
	585	473,475c483
	586	< C<ord> has a two-argument variant that takes a character offset to select
	587	< a single character from a multicharacter string. The offset must be within
	588	< the length of the string:
	589	---
	590	> <p><code>ord</code> 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>
	591	478,479c486
	592	< A negative offset counts backward from the end of the string, so -1 is
	593	< the last character.
	594	---
	595	> <p>A negative offset counts backward from the end of the string, so -1 is the last character.</p>
	596	485c492,494
	597	< X<strings;formatting>
	598	---
	599	> <p><!--
	600	> INDEX: strings;formatting
	601	> --></p>
	602	487,490c496,498
	603	< The C<sprintf>X<sprintf opcode> opcode generates a formatted string from a
	604	< series of values. It takes two arguments: a string specifying the format, and
	605	< an array PMC containing the values to be formatted. The format string and the
	606	< result can be either strings or PMCs:
	607	---
	608	> <p>The <code>sprintf</code><!--
	609	> INDEX: sprintf opcode
	610	> --> 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>
	611	494,510c502,508
	612	< The format string is similar to C's C<sprintf> function with extensions for
	613	< Parrot data types. Each format field in the string starts with a C<%> and ends
	614	< with a character specifying the output format. Table 4.2 lists the available
	615	< output format characters.
	616	<
	617	< Each format field supports several specifier options: R<flags>, R<width>,
	618	< R<precision>, and R<size>. Table 4.3 lists the format flags.
	619	<
	620	< The R<width> is a number defining the minimum width of the output from
	621	< a field. The R<precision> is the maximum width for strings or
	622	< integers, and the number of decimal places for floating-point fields.
	623	< If either R<width> or R<precision> is an asterisk (C<*>), it takes its
	624	< value from the next argument in the PMC.
	625	<
	626	< The R<size> modifier defines the type of the argument the field takes.
	627	< Table 4.4 lists the size flags. The values in the aggregate PMC must
	628	< have a type compatible with the specified R<size>.
	629	---
	630	> <p>The format string is similar to C'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>
688	631	>
689		> Each format field supports several specifier options: R<flags>, R<width>,
690		> R<precision>, and R<size>. Table 4.3 lists the format flags.
	632	> <p>Each format field supports several specifier options: flags, width, precision, and size. Table 4.3 lists the format flags.</p>
691	633	>
692		> The R<width> is a number defining the minimum width of the output from
693		> a field. The R<precision> is the maximum width for strings or
694		> integers, and the number of decimal places for floating-point fields.
695		> If either R<width> or R<precision> is an asterisk (C<*>), it takes its
696		> value from the next argument in the PMC.
	634	> <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-point fields. If either width or precision is an asterisk (<code>*</code>), it takes its value from the next argument in the PMC.</p>
697	635	>
698		> The R<size> modifier defines the type of the argument the field takes.
699		> Table 4.4 lists the size flags. The values in the aggregate PMC must
700		> have a type compatible with the specified R<size>.
701		512c514,519
702		< <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-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>
703		---
704		> The format string of this C<sprintf> example has two format fields. The first,
705		> C<%#Px>, extracts a PMC argument (C<P>) from the aggregate C<$P2> and formats
706		> it as a hexadecimal integer (C<x>) with a leading 0x (C<#>). The second format
707		> field, C<%+2.3Pf>, takes a PMC argument (C<P>) and formats it as a
708		> floating-point number (C<f>) with a minimum of two whole digits and a maximum
709		> of three decimal places (C<2.3>) and a leading sign (C<+>).
710		514c521,522
711		< <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>
712		---
713		> The test files F<t/op/string.t> and F<t/op/sprintf.t> have many more
714		> examples of format strings.
715		519,521c527,529
716		< <p>The <code>join</code><!--
717		< INDEX: join opcode
718		< --> 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>
719		---
720		> The C<join>X<join opcode> opcode joins the elements of an array PMC into
721		> a single string. The first argument separates the individual elements of
722		> the PMC in the final string result.
723		531c539,541
724		< <p>This example builds a <code>Array</code> in <code>$P0</code> with the values <code>"hi"</code>, <code>0</code>, <code>1</code>, <code>0</code>, and <code>"parrot"</code>. It then joins those values (separated by the string <code>"__"</code>) into a single string stored in <code>$S0</code>.</p>
725		---
726		> This example builds a C<Array> in C<$P0> with the values C<"hi">, C<0>, C<1>,
727		> C<0>, and C<"parrot">. It then joins those values (separated by the string
728		> C<"__">) into a single string stored in C<$S0>.
729		536c546,547
730		< <p>Splitting a string yields a new array containing the resulting substrings of the original string.</p>
731		---
732		> Splitting a string yields a new array containing the resulting substrings of
733		> the original string.
734		538c549,551
735		< <p>This example splits the string "abc" 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>
736		---
737		> This example splits the string "abc" into individual characters and stores them
738		> in an array in C<$P0>. It then prints out the first and third elements of the
739		> array.
740		548,550c561,564
741		< <p>The <code>index</code><!--
742		< INDEX: index opcode
743		< --> 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>
744		---
745		> The C<index>X<index opcode> opcode searches for a substring
746		> within a string. If it finds the substring, it returns the position
747		> where the substring was found as a character offset from the beginning
748		> of the string. If it fails to find the substring, it returns -1:
749		556c570,571
750		< <p><code>index</code> also has a three-argument version, where the final argument defines an offset position for starting the search.</p>
751		---
752		> C<index> also has a three-argument version, where the final argument
753		> defines an offset position for starting the search.
754		560c575,576
755		< <p>This example finds the second "eb" in "Beeblebrox" instead of the first, because the search skips the first three characters in the string.</p>
756		---
757		> This example finds the second "eb" in "Beeblebrox" instead of the first,
758		> because the search skips the first three characters in the string.
759		565,571c581,585
760		< <p>The numeric bitwise opcodes also have string variants for AND, OR, and XOR: <code>bors</code><!--
761		< INDEX: bors opcode
762		< -->, <code>bands</code><!--
763		< INDEX: bands opcode
764		< -->, and <code>bxors</code><!--
765		< INDEX: bxors opcode
766		< -->. 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>
767		---
768		> The numeric bitwise opcodes also have string variants for AND, OR, and XOR:
769		> C<bors>X<bors opcode>, C<bands>X<bands opcode>, and C<bxors>X<bxors opcode>.
770		> These take string or string-like PMC arguments and perform the logical
771		> operation on each byte of the strings to produce the result string.
772		> Remember that in-place string operations are no longer available.
773		581c595,596
774		< <p>The bitwise string opcodes produce meaningful results only when used with simple ASCII strings, because Parrot performs bitwise operations per byte.</p>
775		---
776		> The bitwise string opcodes produce meaningful results only when used with
777		> simple ASCII strings, because Parrot performs bitwise operations per byte.
778		586,590c601,604
779		< <p>Strings use copy-on-write (COW)<!--
780		< INDEX: copy-on-write
781		< --><!--
782		< INDEX: COW (copy-on-write)
783		< --> optimizations. A call to <code>$S1 = $S0</code> doesn't immediately make a copy of <code>$S0</code>, 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>
784		---
785		> Strings use copy-on-write (COW)X<copy-on-write>X<COW (copy-on-write)>
786		> optimizations. A call to C<$S1 = $S0> doesn't immediately make a copy of
787		> C<$S0>, it only makes both variables point to the same string. Parrot
788		> doesn't make a copy of the string until one of two strings is modified.
789		597c611,614
790		< <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-on-write is avoiding the cost of copying strings until the copies are necessary.</p>
791		---
792		> Modifying one of the two variables causes Parrot to create a new string. This
793		> example preserves the existing value in C<$S0> and assigns the new value to the
794		> new string in C<$S1>. The benefit of copy-on-write is avoiding the cost of
795		> copying strings until the copies are necessary.
796		602,610c619,637
797		< <p><!--
798		< INDEX: charset
799		< --> <!--
800		< INDEX: ASCII character set
801		< --> <!--
802		< INDEX: encoding
803		< --> 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.</p>
804		<
805		< <p>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.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 <code>encoding:charset:</code>.</p>
806		---
807		> X<charset>
808		> X<ASCII character set>
809		> X<encoding>
810		> Years ago, strings only needed to support the ASCII character set (or
811		> charset), a mapping of 128 bit patterns to symbols and English-language
812		> characters. This worked as long as everyone using a computer read and
813		> wrote English and only used a small handful of punctuation symbols. In
814		> other words, it was woefully insufficient. A modern string system must
815		> manage charsets in order to make sense out of all the string data in the
816		> world. A modern string system must also handle different encodings --
817		> ways to represent various charsets in memory and on disk.
	636	> <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>
	637	514,519c512
	638	< The format string of this C<sprintf> example has two format fields. The first,
	639	< C<%#Px>, extracts a PMC argument (C<P>) from the aggregate C<$P2> and formats
	640	< it as a hexadecimal integer (C<x>) with a leading 0x (C<#>). The second format
	641	< field, C<%+2.3Pf>, takes a PMC argument (C<P>) and formats it as a
	642	< floating-point number (C<f>) with a minimum of two whole digits and a maximum
	643	< of three decimal places (C<2.3>) and a leading sign (C<+>).
	644	---
	645	> <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-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>
	646	521,522c514
	647	< The test files F<t/op/string.t> and F<t/op/sprintf.t> have many more
	648	< examples of format strings.
	649	---
	650	> <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>
	651	527,529c519,521
	652	< The C<join>X<join opcode> opcode joins the elements of an array PMC into
	653	< a single string. The first argument separates the individual elements of
	654	< the PMC in the final string result.
	655	---
	656	> <p>The <code>join</code><!--
	657	> INDEX: join opcode
	658	> --> 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>
	659	539,541c531
	660	< This example builds a C<Array> in C<$P0> with the values C<"hi">, C<0>, C<1>,
	661	< C<0>, and C<"parrot">. It then joins those values (separated by the string
	662	< C<"__">) into a single string stored in C<$S0>.
	663	---
	664	> <p>This example builds a <code>Array</code> in <code>$P0</code> with the values <code>"hi"</code>, <code>0</code>, <code>1</code>, <code>0</code>, and <code>"parrot"</code>. It then joins those values (separated by the string <code>"__"</code>) into a single string stored in <code>$S0</code>.</p>
	665	546,547c536
	666	< Splitting a string yields a new array containing the resulting substrings of
	667	< the original string.
	668	---
	669	> <p>Splitting a string yields a new array containing the resulting substrings of the original string.</p>
	670	549,551c538
	671	< This example splits the string "abc" into individual characters and stores them
	672	< in an array in C<$P0>. It then prints out the first and third elements of the
	673	< array.
	674	---
	675	> <p>This example splits the string "abc" 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>
	676	561,564c548,550
	677	< The C<index>X<index opcode> opcode searches for a substring
	678	< within a string. If it finds the substring, it returns the position
	679	< where the substring was found as a character offset from the beginning
	680	< of the string. If it fails to find the substring, it returns -1:
	681	---
	682	> <p>The <code>index</code><!--
	683	> INDEX: index opcode
	684	> --> 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>
	685	570,571c556
	686	< C<index> also has a three-argument version, where the final argument
	687	< defines an offset position for starting the search.
	688	---
	689	> <p><code>index</code> also has a three-argument version, where the final argument defines an offset position for starting the search.</p>
	690	575,576c560
	691	< This example finds the second "eb" in "Beeblebrox" instead of the first,
	692	< because the search skips the first three characters in the string.
	693	---
	694	> <p>This example finds the second "eb" in "Beeblebrox" instead of the first, because the search skips the first three characters in the string.</p>
	695	581,585c565,571
	696	< The numeric bitwise opcodes also have string variants for AND, OR, and XOR:
	697	< C<bors>X<bors opcode>, C<bands>X<bands opcode>, and C<bxors>X<bxors opcode>.
	698	< These take string or string-like PMC arguments and perform the logical
	699	< operation on each byte of the strings to produce the result string.
	700	< Remember that in-place string operations are no longer available.
	701	---
	702	> <p>The numeric bitwise opcodes also have string variants for AND, OR, and XOR: <code>bors</code><!--
	703	> INDEX: bors opcode
	704	> -->, <code>bands</code><!--
	705	> INDEX: bands opcode
	706	> -->, and <code>bxors</code><!--
	707	> INDEX: bxors opcode
	708	> -->. 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>
	709	595,596c581
	710	< The bitwise string opcodes produce meaningful results only when used with
	711	< simple ASCII strings, because Parrot performs bitwise operations per byte.
	712	---
	713	> <p>The bitwise string opcodes produce meaningful results only when used with simple ASCII strings, because Parrot performs bitwise operations per byte.</p>
	714	601,604c586,590
	715	< Strings use copy-on-write (COW)X<copy-on-write>X<COW (copy-on-write)>
	716	< optimizations. A call to C<$S1 = $S0> doesn't immediately make a copy of
	717	< C<$S0>, it only makes both variables point to the same string. Parrot
	718	< doesn't make a copy of the string until one of two strings is modified.
	719	---
	720	> <p>Strings use copy-on-write (COW)<!--
	721	> INDEX: copy-on-write
	722	> --><!--
	723	> INDEX: COW (copy-on-write)
	724	> --> optimizations. A call to <code>$S1 = $S0</code> doesn't immediately make a copy of <code>$S0</code>, 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>
	725	611,614c597
	726	< Modifying one of the two variables causes Parrot to create a new string. This
	727	< example preserves the existing value in C<$S0> and assigns the new value to the
	728	< new string in C<$S1>. The benefit of copy-on-write is avoiding the cost of
	729	< copying strings until the copies are necessary.
	730	---
	731	> <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-on-write is avoiding the cost of copying strings until the copies are necessary.</p>
	732	619,637c602,610
	733	< X<charset>
	734	< X<ASCII character set>
	735	< X<encoding>
	736	< Years ago, strings only needed to support the ASCII character set (or
	737	< charset), a mapping of 128 bit patterns to symbols and English-language
	738	< characters. This worked as long as everyone using a computer read and
	739	< wrote English and only used a small handful of punctuation symbols. In
	740	< other words, it was woefully insufficient. A modern string system must
	741	< manage charsets in order to make sense out of all the string data in the
	742	< world. A modern string system must also handle different encodings --
	743	< ways to represent various charsets in memory and on disk.
	744	<
	745	< Every string in Parrot has an associated encoding and character set. The default
	746	< charset is 8-bit ASCII, which is almost universally supported. Double-quoted
	747	< string constants can have an optional prefix specifying the string's encoding
	748	< and charset.N<As you might suspect, single-quoted strings do not support this.>
	749	< Parrot tracks information about encoding and charset internally, and
	750	< automatically converts strings when necessary to preserve these
	751	< characteristics. Strings constants may have prefixes of the form C<encoding:charset:>.
	752	---
	753	> <p><!--
	754	> INDEX: charset
	755	> --> <!--
	756	> INDEX: ASCII character set
	757	> --> <!--
	758	> INDEX: encoding
	759	> --> 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.</p>
818	760	>
819		> Every string in Parrot has an associated encoding and character set. The default
820		> charset is 8-bit ASCII, which is almost universally supported. Double-quoted
821		> string constants can have an optional prefix specifying the string's encoding
822		> and charset.N<As you might suspect, single-quoted strings do not support this.>
823		> Parrot tracks information about encoding and charset internally, and
824		> automatically converts strings when necessary to preserve these
825		> characteristics. Strings constants may have prefixes of the form C<encoding:charset:>.
826		616,630c643,663
827		< <p><!--
828		< INDEX: ISO 8859-1 character set
829		< --> <!--
830		< INDEX: Latin 1 character set
831		< --> <!--
832		< INDEX: UCS-2 encoding
833		< --> <!--
834		< INDEX: UTF-8 encoding
835		< --> <!--
836		< INDEX: UTF-16 encoding
837		< --> Parrot supports the character sets <code>ascii</code>, <code>binary</code>, <code>iso-8859-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>
838		<
839		< <p>The <code>binary</code> 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.</p>
840		<
841		< <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-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>
842		---
843		> X<ISO 8859-1 character set>
844		> X<Latin 1 character set>
845		> X<UCS-2 encoding>
846		> X<UTF-8 encoding>
847		> X<UTF-16 encoding>
848		> Parrot supports the character sets C<ascii>, C<binary>, C<iso-8859-1>
849		> (Latin 1), and C<unicode> and the encodings C<fixed_8>, C<ucs2>,
850		> C<utf8>, and C<utf16>.
	761	> <p>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.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 <code>encoding:charset:</code>.</p>
	762	643,663c616,630
	763	< X<ISO 8859-1 character set>
	764	< X<Latin 1 character set>
	765	< X<UCS-2 encoding>
	766	< X<UTF-8 encoding>
	767	< X<UTF-16 encoding>
	768	< Parrot supports the character sets C<ascii>, C<binary>, C<iso-8859-1>
	769	< (Latin 1), and C<unicode> and the encodings C<fixed_8>, C<ucs2>,
	770	< C<utf8>, and C<utf16>.
	771	<
	772	< The C<binary> charset treats the string as a buffer of raw unformatted
	773	< binary data. It isn't really a string per se, because binary data
	774	< contains no readable characters. This exists to support libraries which
	775	< manipulate binary data that doesn't easily fit into any other primitive
	776	< data type.
	777	<
	778	< When Parrot operates on two strings (as in concatenation or comparison), they
	779	< must both use the same character set and encoding. Parrot will automatically
	780	< upgrade one or both of the strings to the next highest compatible format as
	781	< necessary. ASCII strings will automatically upgrade to UTF-8 strings if needed,
	782	< and UTF-8 will upgrade to UTF-16. All of these conversions happen inside
	783	< Parrot, so the programmer doesn't need to worry about the details.
	784	---
	785	> <p><!--
	786	> INDEX: ISO 8859-1 character set
	787	> --> <!--
	788	> INDEX: Latin 1 character set
	789	> --> <!--
	790	> INDEX: UCS-2 encoding
	791	> --> <!--
	792	> INDEX: UTF-8 encoding
	793	> --> <!--
	794	> INDEX: UTF-16 encoding
	795	> --> Parrot supports the character sets <code>ascii</code>, <code>binary</code>, <code>iso-8859-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>
851	796	>
852		> The C<binary> charset treats the string as a buffer of raw unformatted
853		> binary data. It isn't really a string per se, because binary data
854		> contains no readable characters. This exists to support libraries which
855		> manipulate binary data that doesn't easily fit into any other primitive
856		> data type.
	797	> <p>The <code>binary</code> 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.</p>
857	798	>
858		> When Parrot operates on two strings (as in concatenation or comparison), they
859		> must both use the same character set and encoding. Parrot will automatically
860		> upgrade one or both of the strings to the next highest compatible format as
861		> necessary. ASCII strings will automatically upgrade to UTF-8 strings if needed,
862		> and UTF-8 will upgrade to UTF-16. All of these conversions happen inside
863		> Parrot, so the programmer doesn't need to worry about the details.
864		635,639c668,675
865		< <p><!--
866		< INDEX: Polymorphic Containers (PMCs)
867		< --> <!--
868		< INDEX: PMCs (Polymorphic Containers)
869		< --> 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 <code>new</code> opcode creates a new PMC object of the specified type.</p>
870		---
871		> X<Polymorphic Containers (PMCs)>
872		> X<PMCs (Polymorphic Containers)>
873		> Polymorphic Containers (PMCs) are the basis for complex data types and
874		> object-oriented behavior in Parrot. In PIR, any variable that isn't a
875		> low-level integer, number, or string is a PMC. PMC variables act much
876		> like the low-level variables, but you have to instantiate a new PMC
877		> object before you use it. The C<new> opcode creates a new PMC object of
878		> the specified type.
879		644,648c680,687
880		< <p>This example creates a <code>String</code> object, stores it in the PMC register variable <code>$P0</code>, assigns it the value "That's a bollard and not a parrot", and prints it.</p>
881		<
882		< <p>Every PMC has a type that indicates what data it can store and what behavior it supports. The <code>typeof</code><!--
883		< INDEX: typeof opcode
884		< --> opcode reports the type of a PMC. When the result is a string variable, <code>typeof</code> returns the name of the type:</p>
885		---
886		> This example creates a C<String> object, stores it in the PMC register
887		> variable C<$P0>, assigns it the value "That's a bollard and not a
888		> parrot", and prints it.
	799	> <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-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>
	800	668,675c635,639
	801	< X<Polymorphic Containers (PMCs)>
	802	< X<PMCs (Polymorphic Containers)>
	803	< Polymorphic Containers (PMCs) are the basis for complex data types and
	804	< object-oriented behavior in Parrot. In PIR, any variable that isn't a
	805	< low-level integer, number, or string is a PMC. PMC variables act much
	806	< like the low-level variables, but you have to instantiate a new PMC
	807	< object before you use it. The C<new> opcode creates a new PMC object of
	808	< the specified type.
	809	---
	810	> <p><!--
	811	> INDEX: Polymorphic Containers (PMCs)
	812	> --> <!--
	813	> INDEX: PMCs (Polymorphic Containers)
	814	> --> 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 <code>new</code> opcode creates a new PMC object of the specified type.</p>
	815	680,687c644,648
	816	< This example creates a C<String> object, stores it in the PMC register
	817	< variable C<$P0>, assigns it the value "That's a bollard and not a
	818	< parrot", and prints it.
	819	<
	820	< Every PMC has a type that indicates what data it can store and what
	821	< behavior it supports. The C<typeof>X<typeof opcode> opcode reports the
	822	< type of a PMC. When the result is a string variable, C<typeof> returns
	823	< the name of the type:
	824	---
	825	> <p>This example creates a <code>String</code> object, stores it in the PMC register variable <code>$P0</code>, assigns it the value "That's a bollard and not a parrot", and prints it.</p>
889	826	>
890		> Every PMC has a type that indicates what data it can store and what
891		> behavior it supports. The C<typeof>X<typeof opcode> opcode reports the
892		> type of a PMC. When the result is a string variable, C<typeof> returns
893		> the name of the type:
894		653c692,693
895		< <p>When the result is a PMC variable, <code>typeof</code> returns the <code>Class</code> PMC for that object type.</p>
896		---
897		> When the result is a PMC variable, C<typeof> returns the C<Class> PMC
898		> for that object type.
899		658,664c698,707
900		< <p><!--
901		< INDEX: scalar PMCs
902		< --> <!--
903		< INDEX: PMCs (Polymorphic Containers);scalar
904		< --> 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's low-level integers, numbers, and strings.</p>
905		<
906		< <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-level types and their PMC equivalents:</p>
907		---
908		> X<scalar PMCs>
909		> X<PMCs (Polymorphic Containers);scalar>
910		> In most of the examples shown so far, PMCs duplicate the behavior of integers,
911		> numbers, and strings. Parrot provides a set of PMCs for this exact purpose.
912		> C<Integer>, C<Float>, and C<String> are thin overlays on Parrot's low-level
913		> integers, numbers, and strings.
	827	> <p>Every PMC has a type that indicates what data it can store and what behavior it supports. The <code>typeof</code><!--
	828	> INDEX: typeof opcode
	829	> --> opcode reports the type of a PMC. When the result is a string variable, <code>typeof</code> returns the name of the type:</p>
	830	692,693c653
	831	< When the result is a PMC variable, C<typeof> returns the C<Class> PMC
	832	< for that object type.
	833	---
	834	> <p>When the result is a PMC variable, <code>typeof</code> returns the <code>Class</code> PMC for that object type.</p>
	835	698,707c658,664
	836	< X<scalar PMCs>
	837	< X<PMCs (Polymorphic Containers);scalar>
	838	< In most of the examples shown so far, PMCs duplicate the behavior of integers,
	839	< numbers, and strings. Parrot provides a set of PMCs for this exact purpose.
	840	< C<Integer>, C<Float>, and C<String> are thin overlays on Parrot's low-level
	841	< integers, numbers, and strings.
	842	<
	843	< A previous example showed a string literal assigned to a PMC variable of type
	844	< C<String>. Direct assignment of a literal to a PMC works for all the low-level
	845	< types and their PMC equivalents:
	846	---
	847	> <p><!--
	848	> INDEX: scalar PMCs
	849	> --> <!--
	850	> INDEX: PMCs (Polymorphic Containers);scalar
	851	> --> 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's low-level integers, numbers, and strings.</p>
914	852	>
915		> ~~A previous example showed a string literal assigned to a PMC variable of type~~
916		> C<String>. Direct assignment of a literal to a PMC works for all the low-level
917		> types and their PMC equivalents:
918		674,676c717
919		< <p><!--
920		< INDEX: boxing
921		< --></p>
922		---
923		> X<boxing>
924		678c719,722
925		< <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.This conversion of a simpler type to a more complex type is "boxing".</p>
926		---
927		> You may also assign non-constant low-level integer, number, or string registers
928		> ~~directly to a PMC. The PMC handles the conversion from the low-level type to~~
929		> its own internal storage.N<This conversion of a simpler type to a more complex
930		> type is "boxing".>
931		691c735,736
932		< <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>
933		---
934		> The C<box> opcode is a handy shortcut to create the appropriate PMC
935		> object from an integer, number, or string literal or variable.
936		698,700c743,746
937		< ~~<p><!--~~
938		< ~~INDEX: unboxing~~
939		< --> 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.The reverse of "boxing" is "unboxing".</p>
940		---
941		> ~~X<unboxing>~~
942		> ~~In the reverse situation, when assigning a PMC to an integer, number, or~~
943		> string variable, the PMC also has the ability to convert its value to
944		> the low-level type.N<The reverse of "boxing" is "unboxing".>
945		716,724c762,768
946		< ~~<p>This example creates <code>Integer</code><!--~~
947		< ~~INDEX: Integer PMC~~
948		< ~~-->, <code>Float</code><!--~~
949		< ~~INDEX: Float PMC~~
950		< ~~-->, and <code>String</code><!--~~
951		< INDEX: String PMC
952		< --> PMCs, and shows the effect of assigning each one back to a low-level type.</p>
953		<
954		< <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>
955		---
956		> ~~This example creates C<Integer>X<Integer PMC>, C<Float>X<Float PMC>,~~
957		> ~~and C<String>X<String PMC> PMCs, and shows the effect of assigning each~~
958		> ~~one back to a low-level type.~~
	853	> <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-level types and their PMC equivalents:</p>
	854	717c674,676
	855	< X<boxing>
	856	---
	857	> <p><!--
	858	> INDEX: boxing
	859	> --></p>
	860	719,722c678
	861	< You may also assign non-constant low-level integer, number, or string registers
	862	< directly to a PMC. The PMC handles the conversion from the low-level type to
	863	< its own internal storage.N<This conversion of a simpler type to a more complex
	864	< type is "boxing".>
	865	---
	866	> <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.This conversion of a simpler type to a more complex type is "boxing".</p>
	867	735,736c691
	868	< The C<box> opcode is a handy shortcut to create the appropriate PMC
	869	< object from an integer, number, or string literal or variable.
	870	---
	871	> <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>
	872	743,746c698,700
	873	< X<unboxing>
	874	< In the reverse situation, when assigning a PMC to an integer, number, or
	875	< string variable, the PMC also has the ability to convert its value to
	876	< the low-level type.N<The reverse of "boxing" is "unboxing".>
	877	---
	878	> <p><!--
	879	> INDEX: unboxing
	880	> --> 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.The reverse of "boxing" is "unboxing".</p>
	881	762,768c716,724
	882	< This example creates C<Integer>X<Integer PMC>, C<Float>X<Float PMC>,
	883	< and C<String>X<String PMC> PMCs, and shows the effect of assigning each
	884	< one back to a low-level type.
	885	<
	886	< Converting a string to an integer or number only makes sense when the contents
	887	< of the string are a number. The C<String> PMC will attempt to extract a number
	888	< from the beginning of the string, but otherwise will return a false value.
	889	---
	890	> <p>This example creates <code>Integer</code><!--
	891	> INDEX: Integer PMC
	892	> -->, <code>Float</code><!--
	893	> INDEX: Float PMC
	894	> -->, and <code>String</code><!--
	895	> INDEX: String PMC
	896	> --> PMCs, and shows the effect of assigning each one back to a low-level type.</p>
959	897	>
960		> Converting a string to an integer or number only makes sense when the contents
961		> of the string are a number. The C<String> PMC will attempt to extract a number
962		> from the beginning of the string, but otherwise will return a false value.
963		729,733c773,778
964		< <p><!--
965		< INDEX: aggregate PMCs
966		< --> <!--
967		< INDEX: PMCs (Polymorphic Containers);aggregate
968		< --> 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>
969		---
970		> X<aggregate PMCs>
971		> X<PMCs (Polymorphic Containers);aggregate>
972		> PMCs can define complex types that hold multiple values, commonly called
973		> aggregates. Two basic aggregate types are ordered arrays and associative
974		> arrays. The primary difference between these is that ordered arrays use integer
975		> keys for indexes and associative arrays use string keys.
976		735c780,781
977		< <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>
978		---
979		> Aggregate PMCs support the use of numeric or string keys. PIR also offers a
980		> extensive set of operations for manipulating aggregate data types.
981		740,748c786,809
982		< <p><!--
983		< INDEX: arrays
984		< --> <!--
985		< INDEX: ordered arrays
986		< --> 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>
987		<
988		< <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 "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.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.</p>
989		<
990		< <p>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>
991		---
992		> X<arrays>
993		> X<ordered arrays>
994		> Parrot provides several ordered array PMCs, differentiated by whether
995		> the array should store booleans, integers, numbers, strings, or other
996		> PMCs, and whether the array should maintain a fixed size or dynamically
997		> resize for the number of elements it stores.
	898	> <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>
	899	773,778c729,733
	900	< X<aggregate PMCs>
	901	< X<PMCs (Polymorphic Containers);aggregate>
	902	< PMCs can define complex types that hold multiple values, commonly called
	903	< aggregates. Two basic aggregate types are ordered arrays and associative
	904	< arrays. The primary difference between these is that ordered arrays use integer
	905	< keys for indexes and associative arrays use string keys.
	906	---
	907	> <p><!--
	908	> INDEX: aggregate PMCs
	909	> --> <!--
	910	> INDEX: PMCs (Polymorphic Containers);aggregate
	911	> --> 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>
	912	780,781c735
	913	< Aggregate PMCs support the use of numeric or string keys. PIR also offers a
	914	< extensive set of operations for manipulating aggregate data types.
	915	---
	916	> <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>
	917	786,809c740,748
	918	< X<arrays>
	919	< X<ordered arrays>
	920	< Parrot provides several ordered array PMCs, differentiated by whether
	921	< the array should store booleans, integers, numbers, strings, or other
	922	< PMCs, and whether the array should maintain a fixed size or dynamically
	923	< resize for the number of elements it stores.
	924	<
	925	< The core array types are C<FixedPMCArray>, C<ResizablePMCArray>,
	926	< C<FixedIntegerArray>, C<ResizableIntegerArray>, C<FixedFloatArray>,
	927	< C<ResizableFloatArray>, C<FixedStringArray>, C<ResizableStringArray>,
	928	< C<FixedBooleanArray>, and C<ResizableBooleanArray>. The array
	929	< types that start with "Fixed" have a fixed size and do not allow
	930	< elements to be added outside their allocated size. The "Resizable"
	931	< variants automatically extend themselves as more elements are
	932	< added.N<With some additional overhead for checking array bounds and
	933	< reallocating array memory.> The array types that include "String",
	934	< "Integer", or "Boolean" in the name use alternate packing methods for
	935	< greater memory efficiency.
	936	<
	937	< Parrot's core ordered array PMCs all have zero-based integer keys. Extracting
	938	< or inserting an element into the array uses PIR's standard key syntax, with the
	939	< key in square brackets after the variable name. An lvalue key sets the value
	940	< for that key. An rvalue key extracts the value for that key in the aggregate
	941	< to use as the argument value:
	942	---
	943	> <p><!--
	944	> INDEX: arrays
	945	> --> <!--
	946	> INDEX: ordered arrays
	947	> --> 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>
998	948	>
999		> The core array types are C<FixedPMCArray>, C<ResizablePMCArray>,
1000		> C<FixedIntegerArray>, C<ResizableIntegerArray>, C<FixedFloatArray>,
1001		> C<ResizableFloatArray>, C<FixedStringArray>, C<ResizableStringArray>,
1002		> C<FixedBooleanArray>, and C<ResizableBooleanArray>. The array
1003		> types that start with "Fixed" have a fixed size and do not allow
1004		> elements to be added outside their allocated size. The "Resizable"
1005		> variants automatically extend themselves as more elements are
1006		> added.N<With some additional overhead for checking array bounds and
1007		> reallocating array memory.> The array types that include "String",
1008		> "Integer", or "Boolean" in the name use alternate packing methods for
1009		> greater memory efficiency.
	949	> <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 "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.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.</p>
1010	950	>
1011		> Parrot's core ordered array PMCs all have zero-based integer keys. Extracting
1012		> or inserting an element into the array uses PIR's standard key syntax, with the
1013		> key in square brackets after the variable name. An lvalue key sets the value
1014		> for that key. An rvalue key extracts the value for that key in the aggregate
1015		> to use as the argument value:
1016		754c815,817
1017		< <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>
1018		---
1019		> Setting the array to an integer value directly (without a key) sets the number
1020		> of elements of the array. Assigning an array directly to an integer retrieves
1021		> the number of elements of the array.
1022		758c821,822
1023		< <p>This is equivalent to using the <code>elements</code> opcode to retrieve the number of items currently in an array:</p>
1024		---
1025		> This is equivalent to using the C<elements> opcode to retrieve the number of
1026		> items currently in an array:
1027		761c825,829
1028		< <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>
1029		---
1030		> Some other useful instructions for working with ordered arrays are
1031		> C<push>, C<pop>, C<shift>, and C<unshift>, to add or remove elements.
1032		> C<push> and C<pop> work on the end of the array, the highest numbered
1033		> index. C<shift> and C<unshift> work on the start of the array, adding or
1034		> removing the zeroth element, and renumbering all the following elements.
1035		771,777c839,847
1036		< <p><!--
1037		< INDEX: associative arrays
1038		< --> <!--
1039		< INDEX: hashes
1040		< --> <!--
1041		< INDEX: dictionaries
1042		< --> 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 <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>
1043		---
1044		> X<associative arrays>
1045		> X<hashes>
1046		> X<dictionaries>
1047		> An associative array is an unordered aggregate that uses string keys to
1048		> identify elements. You may know them as "hash tables", "hashes", "maps", or
1049		> "dictionaries". Parrot provides one core associative array PMC, called C<Hash>.
1050		> String keys work very much like integer keys. An lvalue key sets the value of
1051		> an element, and an rvalue key extracts the value of an element. The string in
1052		> the key must always be in single or double quotes.
1053		782,784c852,854
1054		< <p>Assigning a <code>Hash</code><!--
1055		< INDEX: Hash PMC
1056		< --> 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>
1057		---
1058		> Assigning a C<Hash>X<Hash PMC> PMC (without a key) to an integer result
1059		> fetches the number of elements in the hash.N<You may not set a C<Hash>
1060		> PMC directly to an integer value.>
1061		787,789c857,860
1062		< <p>The <code>exists</code><!--
1063		< INDEX: exists opcode
1064		< --> 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>
1065		---
1066		> The C<exists>X<exists opcode> opcode tests whether a keyed value exists in an
1067		> aggregate. It returns 1 if it finds the key in the aggregate and 0 otherwise.
1068		> It doesn't care if the value itself is true or false, only that an entry exists
1069		> for that key:
1070		795,797c866,867
1071		< <p>The <code>delete</code><!--
1072		< INDEX: delete opcode
1073		< --> opcode removes an element from an associative array:</p>
1074		---
1075		> The C<delete>X<delete opcode> opcode removes an element from an associative
1076		> array:
1077		803,807c873,878
1078		< <p><!--
1079		< INDEX: iterators
1080		< --> <!--
1081		< INDEX: PMCs (Polymorphic Containers); iterators
1082		< --> 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>
1083		---
1084		> X<iterators>
1085		> X<PMCs (Polymorphic Containers); iterators>
1086		> An iterator extracts values from an aggregate PMC one at a time. Iterators are
1087		> most useful in loops which perform an action on every element in an aggregate.
1088		> The C<iter> opcode creates a new iterator from an aggregate PMC. It takes one
1089		> argument, the PMC over which to iterate:
1090		810,812c881
1091		< <p>The <code>shift</code><!--
1092		< INDEX: shift opcode
1093		< --> opcode extracts the next value from the iterator.</p>
1094		---
1095		> The C<shift>X<shift opcode> opcode extracts the next value from the iterator.
1096		815c884,885
1097		< <p>Evaluating the iterator PMC as a boolean returns whether the iterator has reached the end of the aggregate:</p>
1098		---
1099		> Evaluating the iterator PMC as a boolean returns whether the iterator has
1100		> reached the end of the aggregate:
1101		818,822c888,896
1102		< <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>
1103		<
1104		< <p>Load the iterator constants with the <code>.include</code><!--
1105		< INDEX: .include directive
1106		< --> directive to include the file <em>iterator.pasm</em>. To use them, set the iterator PMC to the value of the constant:</p>
1107		---
1108		> Parrot provides predefined constants for working with iterators.
1109		> C<.ITERATE_FROM_START> and C<.ITERATE_FROM_END> constants select whether an
1110		> ordered array iterator starts from the beginning or end of the array. These
1111		> two constants have no effect on associative array iterators, as their elements
1112		> are unordered.
	951	> <p>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>
	952	815,817c754
	953	< Setting the array to an integer value directly (without a key) sets the number
	954	< of elements of the array. Assigning an array directly to an integer retrieves
	955	< the number of elements of the array.
	956	---
	957	> <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>
	958	821,822c758
	959	< This is equivalent to using the C<elements> opcode to retrieve the number of
	960	< items currently in an array:
	961	---
	962	> <p>This is equivalent to using the <code>elements</code> opcode to retrieve the number of items currently in an array:</p>
	963	825,829c761
	964	< Some other useful instructions for working with ordered arrays are
	965	< C<push>, C<pop>, C<shift>, and C<unshift>, to add or remove elements.
	966	< C<push> and C<pop> work on the end of the array, the highest numbered
	967	< index. C<shift> and C<unshift> work on the start of the array, adding or
	968	< removing the zeroth element, and renumbering all the following elements.
	969	---
	970	> <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>
	971	839,847c771,777
	972	< X<associative arrays>
	973	< X<hashes>
	974	< X<dictionaries>
	975	< An associative array is an unordered aggregate that uses string keys to
	976	< identify elements. You may know them as "hash tables", "hashes", "maps", or
	977	< "dictionaries". Parrot provides one core associative array PMC, called C<Hash>.
	978	< String keys work very much like integer keys. An lvalue key sets the value of
	979	< an element, and an rvalue key extracts the value of an element. The string in
	980	< the key must always be in single or double quotes.
	981	---
	982	> <p><!--
	983	> INDEX: associative arrays
	984	> --> <!--
	985	> INDEX: hashes
	986	> --> <!--
	987	> INDEX: dictionaries
	988	> --> 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 <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>
	989	852,854c782,784
	990	< Assigning a C<Hash>X<Hash PMC> PMC (without a key) to an integer result
	991	< fetches the number of elements in the hash.N<You may not set a C<Hash>
	992	< PMC directly to an integer value.>
	993	---
	994	> <p>Assigning a <code>Hash</code><!--
	995	> INDEX: Hash PMC
	996	> --> 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>
	997	857,860c787,789
	998	< The C<exists>X<exists opcode> opcode tests whether a keyed value exists in an
	999	< aggregate. It returns 1 if it finds the key in the aggregate and 0 otherwise.
	1000	< It doesn't care if the value itself is true or false, only that an entry exists
	1001	< for that key:
	1002	---
	1003	> <p>The <code>exists</code><!--
	1004	> INDEX: exists opcode
	1005	> --> 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>
	1006	866,867c795,797
	1007	< The C<delete>X<delete opcode> opcode removes an element from an associative
	1008	< array:
	1009	---
	1010	> <p>The <code>delete</code><!--
	1011	> INDEX: delete opcode
	1012	> --> opcode removes an element from an associative array:</p>
	1013	873,878c803,807
	1014	< X<iterators>
	1015	< X<PMCs (Polymorphic Containers); iterators>
	1016	< An iterator extracts values from an aggregate PMC one at a time. Iterators are
	1017	< most useful in loops which perform an action on every element in an aggregate.
	1018	< The C<iter> opcode creates a new iterator from an aggregate PMC. It takes one
	1019	< argument, the PMC over which to iterate:
	1020	---
	1021	> <p><!--
	1022	> INDEX: iterators
	1023	> --> <!--
	1024	> INDEX: PMCs (Polymorphic Containers); iterators
	1025	> --> 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>
	1026	881c810,812
	1027	< The C<shift>X<shift opcode> opcode extracts the next value from the iterator.
	1028	---
	1029	> <p>The <code>shift</code><!--
	1030	> INDEX: shift opcode
	1031	> --> opcode extracts the next value from the iterator.</p>
	1032	884,885c815
	1033	< Evaluating the iterator PMC as a boolean returns whether the iterator has
	1034	< reached the end of the aggregate:
	1035	---
	1036	> <p>Evaluating the iterator PMC as a boolean returns whether the iterator has reached the end of the aggregate:</p>
	1037	888,896c818,822
	1038	< Parrot provides predefined constants for working with iterators.
	1039	< C<.ITERATE_FROM_START> and C<.ITERATE_FROM_END> constants select whether an
	1040	< ordered array iterator starts from the beginning or end of the array. These
	1041	< two constants have no effect on associative array iterators, as their elements
	1042	< are unordered.
	1043	<
	1044	< Load the iterator constants with the C<.include>X<.include directive>
	1045	< directive to include the file F<iterator.pasm>. To use them, set the
	1046	< iterator PMC to the value of the constant:
	1047	---
	1048	> <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>
1113	1049	>
1114		> Load the iterator constants with the C<.include>X<.include directive>
1115		> directive to include the file F<iterator.pasm>. To use them, set the
1116		> iterator PMC to the value of the constant:
1117		829c903,906
1118		< <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 <code>goto</code> to checks the boolean value of the iterator and another unconditional <code>goto</code>:</p>
1119		---
1120		> With all of those separate pieces in one place, this example loads the iterator
1121		> constants, creates an ordered array of "a", "b", "c", creates an iterator from
1122		> that array, and then loops over the iterator using a conditional C<goto> to
1123		> checks the boolean value of the iterator and another unconditional C<goto>:
1124		846c923,925
1125		< <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>
1126		---
1127		> Associative array iterators work similarly to ordered array iterators. When
1128		> iterating over associative arrays, the C<shift> opcode extracts keys instead of
1129		> values. The key looks up the value in the original hash PMC.
1130		862c941,951
1131		< <p>This example creates an associative array <code>$P2</code> that contains three keys "a", "b", and "c", 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>
1132		---
1133		> This example creates an associative array C<$P2> that contains three
1134		> keys "a", "b", and "c", assigning them the values 10, 20, and 30. It
1135		> creates an iterator (C<$P1>) from the associative array using the
1136		> C<iter> opcode, and then starts a loop over the iterator. At the start
1137		> of each loop, the C<unless> instruction checks whether the iterator has
1138		> any more elements. If there are no more elements, C<goto> jumps to the
1139		> end of the loop, marked by the label C<iter_end>. If there are more
1140		> elements, the C<shift> opcode extracts the next key. Keyed assignment
1141		> stores the integer value of the element indexed by the key in C<$I9>.
1142		> After printing the integer value, C<goto> jumps back to the start of the
1143		> loop, marked by C<iter_loop>.
1144		867,871c956,962
1145		< <p><!--
1146		< INDEX: keys
1147		< --> <!--
1148		< INDEX: multi-level keys
1149		< --> 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>
1150		---
1151		> X<keys>
1152		> X<multi-level keys>
1153		> Aggregates can hold any data type, including other aggregates.
1154		> Accessing elements deep within nested data structures is a common
1155		> operation, so PIR provides a way to do it in a single instruction.
1156		> Complex keys specify a series of nested data structures, with each
1157		> individual key separated by a semicolon.
1158		881c972,975
1159		< <p>This example builds up a data structure of an associative array containing an ordered array. The complex key <code>["answer"; $I1]</code> retrieves an element of the array within the hash. You can also set a value using a complex key:</p>
1160		---
1161		> This example builds up a data structure of an associative array
1162		> containing an ordered array. The complex key C<["answer"; $I1]>
1163		> retrieves an element of the array within the hash. You can also set a
1164		> value using a complex key:
1165		884c978,979
1166		< <p>The individual keys are integer or string literals, or variables with integer or string values.</p>
1167		---
1168		> The individual keys are integer or string literals, or variables with
1169		> integer or string values.
1170		889,891c984,989
1171		< <p><!--
1172		< INDEX: PMCs (Polymorphic Containers); copying vs. cloning
1173		< --> 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 <code>=</code> 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>
1174		---
1175		> X<PMCs (Polymorphic Containers); copying vs. cloning>
1176		> PMC registers don't directly store the data for a PMC, they only store a
1177		> pointer to the structure that stores the data. As a result, the C<=>
1178		> operator doesn't copy the entire PMC, it only copies the pointer to the
1179		> PMC data. If you later modify the copy of the variable, it will also
1180		> modify the original.
1181		899c997,1000
1182		< <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 "Zaphod", it overwrites the previous value "Ford". Both <code>$P0</code> and <code>$P1</code> refer to the <code>String</code> PMC "Zaphod".</p>
1183		---
1184		> In this example, C<$P0> and C<$P1> are both pointers to the same
1185		> internal data structure. Setting C<$P1> to the string literal
1186		> "Zaphod", it overwrites the previous value "Ford". Both C<$P0> and
1187		> C<$P1> refer to the C<String> PMC "Zaphod".
1188		901,905c1002,1003
1189		< <p>The <code>clone</code> <!--
1190		< INDEX: clone opcode
1191		< --> opcode makes a deep copy of a PMC, instead of copying the pointer like <code>=</code><!--
1192		< INDEX: = operator
1193		< --> does.</p>
1194		---
1195		> The C<clone> X<clone opcode> opcode makes a deep copy of a PMC, instead
1196		> of copying the pointer like C<=>X<= operator> does.
1197		913,919c1011,1018
1198		< <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-level strings, the copies created by <code>clone</code> are copy-on-write<!--
1199		< INDEX: copy-on-write
1200		< --> exactly the same as the copy created by <code>=</code>.</p>
1201		<
1202		< <p>To assign the <i>value</i> of one PMC to another PMC that already exists, use the <code>assign</code><!--
1203		< INDEX: assign opcode
1204		< --> opcode:</p>
1205		---
1206		> This example creates an identical, independent clone of the PMC in
1207		> C<$P0> and puts it in C<$P1>. Later changes to C<$P0> have no effect on
1208		> the PMC in C<$P1>.N<With low-level strings, the copies created by
1209		> C<clone> are copy-on-writeX<copy-on-write> exactly the same as the copy
1210		> created by C<=>.>
	1050	> <p>Load the iterator constants with the <code>.include</code><!--
	1051	> INDEX: .include directive
	1052	> --> directive to include the file <em>iterator.pasm</em>. To use them, set the iterator PMC to the value of the constant:</p>
	1053	903,906c829
	1054	< With all of those separate pieces in one place, this example loads the iterator
	1055	< constants, creates an ordered array of "a", "b", "c", creates an iterator from
	1056	< that array, and then loops over the iterator using a conditional C<goto> to
	1057	< checks the boolean value of the iterator and another unconditional C<goto>:
	1058	---
	1059	> <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 <code>goto</code> to checks the boolean value of the iterator and another unconditional <code>goto</code>:</p>
	1060	923,925c846
	1061	< Associative array iterators work similarly to ordered array iterators. When
	1062	< iterating over associative arrays, the C<shift> opcode extracts keys instead of
	1063	< values. The key looks up the value in the original hash PMC.
	1064	---
	1065	> <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>
	1066	941,951c862
	1067	< This example creates an associative array C<$P2> that contains three
	1068	< keys "a", "b", and "c", assigning them the values 10, 20, and 30. It
	1069	< creates an iterator (C<$P1>) from the associative array using the
	1070	< C<iter> opcode, and then starts a loop over the iterator. At the start
	1071	< of each loop, the C<unless> instruction checks whether the iterator has
	1072	< any more elements. If there are no more elements, C<goto> jumps to the
	1073	< end of the loop, marked by the label C<iter_end>. If there are more
	1074	< elements, the C<shift> opcode extracts the next key. Keyed assignment
	1075	< stores the integer value of the element indexed by the key in C<$I9>.
	1076	< After printing the integer value, C<goto> jumps back to the start of the
	1077	< loop, marked by C<iter_loop>.
	1078	---
	1079	> <p>This example creates an associative array <code>$P2</code> that contains three keys "a", "b", and "c", 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>
	1080	956,962c867,871
	1081	< X<keys>
	1082	< X<multi-level keys>
	1083	< Aggregates can hold any data type, including other aggregates.
	1084	< Accessing elements deep within nested data structures is a common
	1085	< operation, so PIR provides a way to do it in a single instruction.
	1086	< Complex keys specify a series of nested data structures, with each
	1087	< individual key separated by a semicolon.
	1088	---
	1089	> <p><!--
	1090	> INDEX: keys
	1091	> --> <!--
	1092	> INDEX: multi-level keys
	1093	> --> 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>
	1094	972,975c881
	1095	< This example builds up a data structure of an associative array
	1096	< containing an ordered array. The complex key C<["answer"; $I1]>
	1097	< retrieves an element of the array within the hash. You can also set a
	1098	< value using a complex key:
	1099	---
	1100	> <p>This example builds up a data structure of an associative array containing an ordered array. The complex key <code>["answer"; $I1]</code> retrieves an element of the array within the hash. You can also set a value using a complex key:</p>
	1101	978,979c884
	1102	< The individual keys are integer or string literals, or variables with
	1103	< integer or string values.
	1104	---
	1105	> <p>The individual keys are integer or string literals, or variables with integer or string values.</p>
	1106	984,989c889,891
	1107	< X<PMCs (Polymorphic Containers); copying vs. cloning>
	1108	< PMC registers don't directly store the data for a PMC, they only store a
	1109	< pointer to the structure that stores the data. As a result, the C<=>
	1110	< operator doesn't copy the entire PMC, it only copies the pointer to the
	1111	< PMC data. If you later modify the copy of the variable, it will also
	1112	< modify the original.
	1113	---
	1114	> <p><!--
	1115	> INDEX: PMCs (Polymorphic Containers); copying vs. cloning
	1116	> --> 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 <code>=</code> 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>
	1117	997,1000c899
	1118	< In this example, C<$P0> and C<$P1> are both pointers to the same
	1119	< internal data structure. Setting C<$P1> to the string literal
	1120	< "Zaphod", it overwrites the previous value "Ford". Both C<$P0> and
	1121	< C<$P1> refer to the C<String> PMC "Zaphod".
	1122	---
	1123	> <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 "Zaphod", it overwrites the previous value "Ford". Both <code>$P0</code> and <code>$P1</code> refer to the <code>String</code> PMC "Zaphod".</p>
	1124	1002,1003c901,905
	1125	< The C<clone> X<clone opcode> opcode makes a deep copy of a PMC, instead
	1126	< of copying the pointer like C<=>X<= operator> does.
	1127	---
	1128	> <p>The <code>clone</code> <!--
	1129	> INDEX: clone opcode
	1130	> --> opcode makes a deep copy of a PMC, instead of copying the pointer like <code>=</code><!--
	1131	> INDEX: = operator
	1132	> --> does.</p>
	1133	1011,1018c913,919
	1134	< This example creates an identical, independent clone of the PMC in
	1135	< C<$P0> and puts it in C<$P1>. Later changes to C<$P0> have no effect on
	1136	< the PMC in C<$P1>.N<With low-level strings, the copies created by
	1137	< C<clone> are copy-on-writeX<copy-on-write> exactly the same as the copy
	1138	< created by C<=>.>
	1139	<
	1140	< To assign the I<value> of one PMC to another PMC that already exists, use the
	1141	< C<assign>X<assign opcode> opcode:
	1142	---
	1143	> <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-level strings, the copies created by <code>clone</code> are copy-on-write<!--
	1144	> INDEX: copy-on-write
	1145	> --> exactly the same as the copy created by <code>=</code>.</p>
1211	1146	>
1212		> To assign the I<value> of one PMC to another PMC that already exists, use the
1213		> C<assign>X<assign opcode> opcode:
1214		928c1027,1032
1215		< <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'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>
1216		---
1217		> This example creates two C<Integer> PMCs, C<$P1> and C<$P2>, and gives the
1218		> first one the value 42. It then uses C<assign> to pass the same integer value
1219		> on to C<$P1>. Though C<$P0> increments, C<$P1> doesn't change. The result for
1220		> C<assign> must have an existing object of the right type in it, because
1221		> C<assign> neither creates a new duplicate object (as does C<clone>) or reuses
1222		> the source object (as does C<=>).
1223		933,937c1037,1038
1224		< <p><!--
1225		< INDEX: properties
1226		< --> <!--
1227		< INDEX: PMCs (Polymorphic Containers); properties
1228		< --></p>
1229		---
1230		> X<properties>
1231		> X<PMCs (Polymorphic Containers); properties>
1232		939c1040,1041
1233		< <p>PMCs can have additional values attached to them as "properties" of the PMC. Most properties hold extra metadata about the PMC.</p>
1234		---
1235		> PMCs can have additional values attached to them as "properties" of the
1236		> PMC. Most properties hold extra metadata about the PMC.
1237		941,943c1043,1045
1238		< <p>The <code>setprop</code><!--
1239		< INDEX: setprop opcode
1240		< --> 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>
1241		---
1242		> The C<setprop>X<setprop opcode> opcode sets the value of a named property on a
1243		> PMC. It takes three arguments: the PMC on which to set a property, the name of
1244		> the property, and a PMC containing the value of the property.
1245		946,948c1048,1050
1246		< <p>The <code>getprop</code><!--
1247		< INDEX: getprop opcode
1248		< --> 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>
1249		---
1250		> The C<getprop>X<getprop opcode> opcode returns the value of a property. It
1251		> takes two arguments: the name of the property and the PMC from which to
1252		> retrieve the property value.
1253		951c1053,1056
1254		< <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 "eric" 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 "eric" on <code>$P0</code> and stores it in <code>$P2</code>.</p>
1255		---
1256		> This example creates a C<String> object in C<$P0> and an C<Integer> object with
1257		> the value 1 in C<$P1>. C<setprop> sets a property named "eric" on the object in
1258		> C<$P0> and gives the property the value of C<$P1>. C<getprop> retrieves the
1259		> value of the property "eric" on C<$P0> and stores it in C<$P2>.
1260		962c1067,1068
1261		< <p>Parrot stores PMC properties in an associative array where the name of the property is the key.</p>
1262		---
1263		> Parrot stores PMC properties in an associative array where the name of the
1264		> property is the key.
1265		964,966c1070
1266		< <p><code>delprop</code><!--
1267		< INDEX: delprop opcode
1268		< --> deletes a property from a PMC.</p>
1269		---
1270		> C<delprop>X<delprop opcode> deletes a property from a PMC.
1271		969,971c1073,1074
1272		< <p>You can fetch a complete hash of all properties on a PMC with <code>prophash</code><!--
1273		< INDEX: prophash opcode
1274		< -->:</p>
1275		---
1276		> You can fetch a complete hash of all properties on a PMC with
1277		> C<prophash>X<prophash opcode>:
1278		974c1077
1279		< <p>Fetching the value of a non-existent property returns an <code>Undef</code> PMC.</p>
1280		---
1281		> Fetching the value of a non-existent property returns an C<Undef> PMC.
1282		979,991c1082,1104
1283		< <p><!--
1284		< INDEX: vtable functions
1285		< --> You may have noticed that a simple operation sometimes has a different effect on different PMCs. Assigning a low-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>
1286		<
1287		< <p>Every PMC defines a standard set of low-level operations called vtable functions. When you perform an assignment like:</p>
1288		<
1289		< <pre> $P0 = 5</pre>
1290		<
1291		< <p>... Parrot calls the <code>set_integer_native</code> vtable function on the PMC referred to by register <code>$P0</code>.</p>
1292		<
1293		< <p><!--
1294		< INDEX: polymorphic substitution
1295		< --> Parrot has a fixed set of vtable functions, so that any PMC can stand in for any other PMC; they're polymorphic.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>
1296		---
1297		> X<vtable functions>
1298		> You may have noticed that a simple operation sometimes has a different effect
1299		> on different PMCs. Assigning a low-level integer value to a C<Integer> PMC sets
1300		> its integer value of the PMC, but assigning that same integer to an ordered
1301		> array sets the size of the array.
	1147	> <p>To assign the <i>value</i> of one PMC to another PMC that already exists, use the <code>assign</code><!--
	1148	> INDEX: assign opcode
	1149	> --> opcode:</p>
	1150	1027,1032c928
	1151	< This example creates two C<Integer> PMCs, C<$P1> and C<$P2>, and gives the
	1152	< first one the value 42. It then uses C<assign> to pass the same integer value
	1153	< on to C<$P1>. Though C<$P0> increments, C<$P1> doesn't change. The result for
	1154	< C<assign> must have an existing object of the right type in it, because
	1155	< C<assign> neither creates a new duplicate object (as does C<clone>) or reuses
	1156	< the source object (as does C<=>).
	1157	---
	1158	> <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'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>
	1159	1037,1038c933,937
	1160	< X<properties>
	1161	< X<PMCs (Polymorphic Containers); properties>
	1162	---
	1163	> <p><!--
	1164	> INDEX: properties
	1165	> --> <!--
	1166	> INDEX: PMCs (Polymorphic Containers); properties
	1167	> --></p>
	1168	1040,1041c939
	1169	< PMCs can have additional values attached to them as "properties" of the
	1170	< PMC. Most properties hold extra metadata about the PMC.
	1171	---
	1172	> <p>PMCs can have additional values attached to them as "properties" of the PMC. Most properties hold extra metadata about the PMC.</p>
	1173	1043,1045c941,943
	1174	< The C<setprop>X<setprop opcode> opcode sets the value of a named property on a
	1175	< PMC. It takes three arguments: the PMC on which to set a property, the name of
	1176	< the property, and a PMC containing the value of the property.
	1177	---
	1178	> <p>The <code>setprop</code><!--
	1179	> INDEX: setprop opcode
	1180	> --> 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>
	1181	1048,1050c946,948
	1182	< The C<getprop>X<getprop opcode> opcode returns the value of a property. It
	1183	< takes two arguments: the name of the property and the PMC from which to
	1184	< retrieve the property value.
	1185	---
	1186	> <p>The <code>getprop</code><!--
	1187	> INDEX: getprop opcode
	1188	> --> 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>
	1189	1053,1056c951
	1190	< This example creates a C<String> object in C<$P0> and an C<Integer> object with
	1191	< the value 1 in C<$P1>. C<setprop> sets a property named "eric" on the object in
	1192	< C<$P0> and gives the property the value of C<$P1>. C<getprop> retrieves the
	1193	< value of the property "eric" on C<$P0> and stores it in C<$P2>.
	1194	---
	1195	> <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 "eric" 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 "eric" on <code>$P0</code> and stores it in <code>$P2</code>.</p>
	1196	1067,1068c962
	1197	< Parrot stores PMC properties in an associative array where the name of the
	1198	< property is the key.
	1199	---
	1200	> <p>Parrot stores PMC properties in an associative array where the name of the property is the key.</p>
	1201	1070c964,966
	1202	< C<delprop>X<delprop opcode> deletes a property from a PMC.
	1203	---
	1204	> <p><code>delprop</code><!--
	1205	> INDEX: delprop opcode
	1206	> --> deletes a property from a PMC.</p>
	1207	1073,1074c969,971
	1208	< You can fetch a complete hash of all properties on a PMC with
	1209	< C<prophash>X<prophash opcode>:
	1210	---
	1211	> <p>You can fetch a complete hash of all properties on a PMC with <code>prophash</code><!--
	1212	> INDEX: prophash opcode
	1213	> -->:</p>
	1214	1077c974
	1215	< Fetching the value of a non-existent property returns an C<Undef> PMC.
	1216	---
	1217	> <p>Fetching the value of a non-existent property returns an <code>Undef</code> PMC.</p>
	1218	1082,1104c979,991
	1219	< X<vtable functions>
	1220	< You may have noticed that a simple operation sometimes has a different effect
	1221	< on different PMCs. Assigning a low-level integer value to a C<Integer> PMC sets
	1222	< its integer value of the PMC, but assigning that same integer to an ordered
	1223	< array sets the size of the array.
	1224	<
	1225	< Every PMC defines a standard set of low-level operations called vtable
	1226	< functions. When you perform an assignment like:
	1227	<
	1228	< $P0 = 5
	1229	<
	1230	<
	1231	< ... Parrot calls the C<set_integer_native> vtable function on the PMC referred
	1232	< to by register C<$P0>.
	1233	<
	1234	< X<polymorphic substitution>
	1235	< Parrot has a fixed set of vtable functions, so that any PMC can stand in for
	1236	< any other PMC; they're polymorphic.N<Hence the name "Polymorphic Container".>
	1237	< Every PMC defines some behavior for every vtable function. The default behavior
	1238	< is to throw an exception reporting that the PMC doesn't implement that vtable
	1239	< function. The full set of vtable functions for a PMC defines the PMC's basic
	1240	< interface, but PMCs may also define methods to extend their behavior beyond the
	1241	< vtable set.
	1242	---
	1243	> <p><!--
	1244	> INDEX: vtable functions
	1245	> --> You may have noticed that a simple operation sometimes has a different effect on different PMCs. Assigning a low-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>
1302	1246	>
1303		> Every PMC defines a standard set of low-level operations called vtable
1304		> functions. When you perform an assignment like:
	1247	> <p>Every PMC defines a standard set of low-level operations called vtable functions. When you perform an assignment like:</p>
1305	1248	>
1306		> ~~$P0 = 5~~
	1249	> <pre> $P0 = 5</pre>
1307	1250	>
	1251	> <p>... Parrot calls the <code>set_integer_native</code> vtable function on the PMC referred to by register <code>$P0</code>.</p>
1308	1252	>
1309		> ... Parrot calls the C<set_integer_native> vtable function on the PMC referred
1310		> to by register C<$P0>.
	1253	> <p><!--
	1254	> INDEX: polymorphic substitution
	1255	> --> Parrot has a fixed set of vtable functions, so that any PMC can stand in for any other PMC; they're polymorphic.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>
	1256	1109,1120c996,1006
	1257	< X<namespaces>
	1258	< X<global variables>
	1259	< Parrot performs operations on variables stored in small register sets local to
	1260	< each subroutine. For more complex tasks,N<...and for most high-level languages
	1261	< that Parrot supports.> it's also useful to have variables that live beyond the
	1262	< scope of a single subroutine. These variables may be global to the entire
	1263	< program or restricted to a particular library. Parrot stores long-lived
	1264	< variables in a hierarchy of namespaces.
	1265	<
	1266	< The opcodes C<set_global>X<set_global opcode> and
	1267	< C<get_global>X<get_global opcode> store and fetch a variable in a
	1268	< namespace:
	1269	---
	1270	> <p><!--
	1271	> INDEX: namespaces
	1272	> --> <!--
	1273	> INDEX: global variables
	1274	> --> Parrot performs operations on variables stored in small register sets local to each subroutine. For more complex tasks,...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.</p>
1311	1275	>
1312		> X<polymorphic substitution>
1313		> Parrot has a fixed set of vtable functions, so that any PMC can stand in for
1314		> any other PMC; they're polymorphic.N<Hence the name "Polymorphic Container".>
1315		> Every PMC defines some behavior for every vtable function. The default behavior
1316		> is to throw an exception reporting that the PMC doesn't implement that vtable
1317		> function. The full set of vtable functions for a PMC defines the PMC's basic
1318		> interface, but PMCs may also define methods to extend their behavior beyond the
1319		> vtable set.
1320		996,1006c1109,1120
1321		< <p><!--
1322		< INDEX: namespaces
1323		< --> <!--
1324		< INDEX: global variables
1325		< --> Parrot performs operations on variables stored in small register sets local to each subroutine. For more complex tasks,...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.</p>
1326		<
1327		< <p>The opcodes <code>set_global</code><!--
1328		< INDEX: set_global opcode
1329		< --> and <code>get_global</code><!--
1330		< INDEX: get_global opcode
1331		< --> store and fetch a variable in a namespace:</p>
1332		---
1333		> X<namespaces>
1334		> X<global variables>
1335		> Parrot performs operations on variables stored in small register sets local to
1336		> each subroutine. For more complex tasks,N<...and for most high-level languages
1337		> that Parrot supports.> it's also useful to have variables that live beyond the
1338		> scope of a single subroutine. These variables may be global to the entire
1339		> program or restricted to a particular library. Parrot stores long-lived
1340		> variables in a hierarchy of namespaces.
	1276	> <p>The opcodes <code>set_global</code><!--
	1277	> INDEX: set_global opcode
	1278	> --> and <code>get_global</code><!--
	1279	> INDEX: get_global opcode
	1280	> --> store and fetch a variable in a namespace:</p>
	1281	1128,1144c1014,1018
	1282	< The first two statements in this example create a C<String> PMC in
	1283	< C<$P0> and assign it a value. In the third statement, C<set_global>
	1284	< stores that PMC as the named global variable C<bee>. At some later
	1285	< point in the program, C<get_global> retrieves the global variable by
	1286	< name, and stores it in C<$P1> to print.
	1287	<
	1288	< Namespaces can only store PMC variables. Parrot boxes all primitive integer,
	1289	< number, or string values into the corresponding PMCs before storing them in a
	1290	< namespace.
	1291	<
	1292	< The name of every variable stored in a particular namespace must be
	1293	< unique. You can't have store both an C<Integer> PMC and an array PMC
	1294	< both named "bee", stored in the same namespace.N<You may wonder why
	1295	< anyone would want to do this. We wonder the same thing, but Perl 5 does
	1296	< it all the time. The Perl 6 implementation on Parrot includes type
	1297	< sigils in the names of the variables it stores in namespaces so each
	1298	< name is unique, e.g. C<$bee>, C<@bee>....>
	1299	---
	1300	> <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>
1341	1301	>
1342		> The opcodes C<set_global>X<set_global opcode> and
1343		> C<get_global>X<get_global opcode> store and fetch a variable in a
1344		> namespace:
1345		1014,1018c1128,1144
1346		< <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>
1347		<
1348		< <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>
1349		<
1350		< <p>The name of every variable stored in a particular namespace must be unique. You can't have store both an <code>Integer</code> PMC and an array PMC both named "bee", 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>
1351		---
1352		> The first two statements in this example create a C<String> PMC in
1353		> C<$P0> and assign it a value. In the third statement, C<set_global>
1354		> stores that PMC as the named global variable C<bee>. At some later
1355		> point in the program, C<get_global> retrieves the global variable by
1356		> name, and stores it in C<$P1> to print.
	1302	> <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>
1357	1303	>
1358		> Namespaces can only store PMC variables. Parrot boxes all primitive integer,
1359		> number, or string values into the corresponding PMCs before storing them in a
1360		> namespace.
	1304	> <p>The name of every variable stored in a particular namespace must be unique. You can't have store both an <code>Integer</code> PMC and an array PMC both named "bee", 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>
	1305	1149,1150c1023,1029
	1306	< X<hierarchical namespaces>
	1307	< X<namespaces; hierarchy>
	1308	---
	1309	> <p><!--
	1310	> INDEX: hierarchical namespaces
	1311	> --> <!--
	1312	> INDEX: namespaces; hierarchy
	1313	> --></p>
1361	1314	>
1362		> The name of every variable stored in a particular namespace must be
1363		> unique. You can't have store both an C<Integer> PMC and an array PMC
1364		> both named "bee", stored in the same namespace.N<You may wonder why
1365		> anyone would want to do this. We wonder the same thing, but Perl 5 does
1366		> it all the time. The Perl 6 implementation on Parrot includes type
1367		> sigils in the names of the variables it stores in namespaces so each
1368		> name is unique, e.g. C<$bee>, C<@bee>....>
1369		1023,1029c1149,1150
1370		< <p><!--
1371		< INDEX: hierarchical namespaces
1372		< --> <!--
1373		< INDEX: namespaces; hierarchy
1374		< --></p>
1375		<
1376		< <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 <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>
1377		---
1378		> X<hierarchical namespaces>
1379		> X<namespaces; hierarchy>
1380		1031c1152,1162
1381		< <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>
1382		---
1383		> A single global namespace would be far too limiting for most languages or
1384		> applications. The risk of accidental collisions -- where two libraries try to
1385		> use the same name for some variable -- would be quite high for larger code
1386		> bases. Parrot maintains a collection of namespaces arranged as a tree, with the
1387		> C<parrot> namespace as the root. Every namespace you declare is a child of the
1388		> C<parrot> namespace (or a child of a child....).
	1315	> <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 <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>
	1316	1152,1162c1031
	1317	< A single global namespace would be far too limiting for most languages or
	1318	< applications. The risk of accidental collisions -- where two libraries try to
	1319	< use the same name for some variable -- would be quite high for larger code
	1320	< bases. Parrot maintains a collection of namespaces arranged as a tree, with the
	1321	< C<parrot> namespace as the root. Every namespace you declare is a child of the
	1322	< C<parrot> namespace (or a child of a child....).
	1323	<
	1324	< The C<set_global> and C<get_global> opcodes both have alternate forms that take
	1325	< a key name to access a variable in a particular namespace within the tree. This
	1326	< code example stores a variable as C<bill> in the Duck namespace and retrieves
	1327	< it again:
	1328	---
	1329	> <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>
	1330	1166,1168c1035
	1331	< The key name for the namespace can have multiple levels, which correspond to
	1332	< levels in the namespace hierarchy. This example stores a variable as C<bill> in
	1333	< the Electric namespace under the General namespace in the hierarchy.
	1334	---
	1335	> <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>
	1336	1172,1173c1039,1043
	1337	< X<root namespace>
	1338	< X<namespaces; root>
	1339	---
	1340	> <p><!--
	1341	> INDEX: root namespace
	1342	> --> <!--
	1343	> INDEX: namespaces; root
	1344	> --></p>
	1345	1175,1181c1045,1047
	1346	< The C<set_global> and C<get_global> opcode operate on the currently selected
	1347	< namespace. The default top-level namespace is the "root" namespace. The
	1348	< C<.namespace>X<.namespace directive> directive allows you to declare any
	1349	< namespace for subsequent code. If you select the General Electric
	1350	< namespace, then store or retrieve the C<bill> variable without
	1351	< specifying a namespace, you will work with the General Electric bill,
	1352	< not the Duck bill.
	1353	---
	1354	> <p>The <code>set_global</code> and <code>get_global</code> opcode operate on the currently selected namespace. The default top-level namespace is the "root" namespace. The <code>.namespace</code><!--
	1355	> INDEX: .namespace directive
	1356	> --> 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>
	1357	1183c1049
	1358	< .namespace ["General";"Electric"]
	1359	---
	1360	> <pre> .namespace ["General";"Electric"]
	1361	1185,1186c1051,1052
	1362	< set_global "bill", $P0
	1363	< $P1 = get_global "bill"
	1364	---
	1365	> set_global "bill", $P0
	1366	> $P1 = get_global "bill"</pre>
	1367	1187a1054
	1368	> <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>
	1369	1189,1191c1056
	1370	< Passing an empty key to the C<.namespace> directive resets the selected
	1371	< namespace to the root namespace. The brackets are required even when the
	1372	< key is empty.
	1373	---
	1374	> <pre> .namespace [ ]</pre>
	1375	1193,1202c1058,1062
	1376	< .namespace [ ]
	1377	<
	1378	<
	1379	< When you need to be absolutely sure you're working with the root namespace
	1380	< regardless of what namespace is currently active, use the
	1381	< C<set_root_global>X<set_root_global opcode> and
	1382	< C<get_root_global>X<get_root_global opcode> opcodes instead of
	1383	< C<set_global> and C<get_global>. This example sets and retrieves the
	1384	< variable C<bill> in the Dollar namespace, which is directly under the
	1385	< root namespace:
	1386	---
	1387	> <p>When you need to be absolutely sure you're working with the root namespace regardless of what namespace is currently active, use the <code>set_root_global</code><!--
	1388	> INDEX: set_root_global opcode
	1389	> --> and <code>get_root_global</code><!--
	1390	> INDEX: get_root_global opcode
	1391	> --> 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>
	1392	1206,1222c1066,1080
	1393	< X<HLL namespaces>
	1394	< X<namespaces; hll>
	1395	< To prevent further collisions, each high-level language running on
	1396	< Parrot operates within its own virtual namespace root. The default
	1397	< virtual root is C<parrot>, and the C<.HLL>X<.HLL directive> directive
	1398	< (for I<H>igh-I<L>evel I<L>anguage) selects an alternate virtual root for
	1399	< a particular high-level language:
	1400	<
	1401	< .HLL 'ruby'
	1402	<
	1403	<
	1404	< The C<set_hll_global>X<set_hll_global opcode> and
	1405	< C<get_hll_global>X<get_hll_global opcode> opcodes are like
	1406	< C<set_root_global> and C<get_root_global>, except they always operate on
	1407	< the virtual root for the currently selected HLL. This example stores and
	1408	< retrieves a C<bill> variable in the Euro namespace, under the Dutch HLL
	1409	< namespace root:
	1410	---
	1411	> <p><!--
	1412	> INDEX: HLL namespaces
	1413	> --> <!--
	1414	> INDEX: namespaces; hll
	1415	> --> To prevent further collisions, each high-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><!--
	1416	> INDEX: .HLL directive
	1417	> --> directive (for <i>H</i>igh-<i>L</i>evel <i>L</i>anguage) selects an alternate virtual root for a particular high-level language:</p>
1389	1418	>
1390		> The C<set_global> and C<get_global> opcodes both have alternate forms that take
1391		> a key name to access a variable in a particular namespace within the tree. This
1392		> code example stores a variable as C<bill> in the Duck namespace and retrieves
1393		> it again:
1394		1035c1166,1168
1395		< <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>
1396		---
1397		> The key name for the namespace can have multiple levels, which correspond to
1398		> levels in the namespace hierarchy. This example stores a variable as C<bill> in
1399		> the Electric namespace under the General namespace in the hierarchy.
1400		1039,1043c1172,1173
1401		< <p><!--
1402		< INDEX: root namespace
1403		< --> <!--
1404		< INDEX: namespaces; root
1405		< --></p>
1406		---
1407		> X<root namespace>
1408		> X<namespaces; root>
1409		1045,1047c1175,1181
1410		< <p>The <code>set_global</code> and <code>get_global</code> opcode operate on the currently selected namespace. The default top-level namespace is the "root" namespace. The <code>.namespace</code><!--
1411		< INDEX: .namespace directive
1412		< --> 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>
1413		---
1414		> The C<set_global> and C<get_global> opcode operate on the currently selected
1415		> namespace. The default top-level namespace is the "root" namespace. The
1416		> C<.namespace>X<.namespace directive> directive allows you to declare any
1417		> namespace for subsequent code. If you select the General Electric
1418		> namespace, then store or retrieve the C<bill> variable without
1419		> specifying a namespace, you will work with the General Electric bill,
1420		> not the Duck bill.
1421		1049c1183
1422		< <pre> .namespace ["General";"Electric"]
1423		---
1424		> .namespace ["General";"Electric"]
1425		1051,1052c1185,1186
1426		< set_global "bill", $P0
1427		< $P1 = get_global "bill"</pre>
1428		---
1429		> set_global "bill", $P0
1430		> $P1 = get_global "bill"
1431		1054d1187
1432		< <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>
1433		1056c1189,1191
1434		< <pre> .namespace [ ]</pre>
1435		---
1436		> Passing an empty key to the C<.namespace> directive resets the selected
1437		> namespace to the root namespace. The brackets are required even when the
1438		> key is empty.
1439		1058,1062c1193,1202
1440		< <p>When you need to be absolutely sure you're working with the root namespace regardless of what namespace is currently active, use the <code>set_root_global</code><!--
1441		< INDEX: set_root_global opcode
1442		< --> and <code>get_root_global</code><!--
1443		< INDEX: get_root_global opcode
1444		< --> 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>
1445		---
1446		> .namespace [ ]
	1419	> <pre> .HLL 'ruby'</pre>
1447	1420	>
1448		>
1449		> When you need to be absolutely sure you're working with the root namespace
1450		> regardless of what namespace is currently active, use the
1451		> C<set_root_global>X<set_root_global opcode> and
1452		> C<get_root_global>X<get_root_global opcode> opcodes instead of
1453		> C<set_global> and C<get_global>. This example sets and retrieves the
1454		> variable C<bill> in the Dollar namespace, which is directly under the
1455		> root namespace:
1456		1066,1080c1206,1222
1457		< <p><!--
1458		< INDEX: HLL namespaces
1459		< --> <!--
1460		< INDEX: namespaces; hll
1461		< --> To prevent further collisions, each high-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><!--
1462		< INDEX: .HLL directive
1463		< --> directive (for <i>H</i>igh-<i>L</i>evel <i>L</i>anguage) selects an alternate virtual root for a particular high-level language:</p>
1464		<
1465		< <pre> .HLL 'ruby'</pre>
1466		<
1467		< <p>The <code>set_hll_global</code><!--
1468		< INDEX: set_hll_global opcode
1469		< --> and <code>get_hll_global</code><!--
1470		< INDEX: get_hll_global opcode
1471		< --> 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>
1472		---
1473		> X<HLL namespaces>
1474		> X<namespaces; hll>
1475		> To prevent further collisions, each high-level language running on
1476		> Parrot operates within its own virtual namespace root. The default
1477		> virtual root is C<parrot>, and the C<.HLL>X<.HLL directive> directive
1478		> (for I<H>igh-I<L>evel I<L>anguage) selects an alternate virtual root for
1479		> a particular high-level language:
1480		>
1481		> .HLL 'ruby'
1482		>
1483		>
1484		> The C<set_hll_global>X<set_hll_global opcode> and
1485		> C<get_hll_global>X<get_hll_global opcode> opcodes are like
1486		> C<set_root_global> and C<get_root_global>, except they always operate on
1487		> the virtual root for the currently selected HLL. This example stores and
1488		> retrieves a C<bill> variable in the Euro namespace, under the Dutch HLL
1489		> namespace root:
1490		1082c1224
1491		< <pre> .HLL 'Dutch'
1492		---
1493		> .HLL 'Dutch'
1494		1084,1085c1226,1228
1495		< set_hll_global ["Euro"], "bill", $P0
1496		< $P1 = get_hll_global ["Euro"], "bill"</pre>
1497		---
1498		> set_hll_global ["Euro"], "bill", $P0
1499		> $P1 = get_hll_global ["Euro"], "bill"
1500		>
1501		1090,1094c1233,1238
1502		< <p><!--
1503		< INDEX: NameSpace PMC
1504		< --> Namespaces are just PMCs. They implement the standard vtable functions and a few extra methods. The <code>get_namespace</code><!--
1505		< INDEX: get_namespace opcode
1506		< --> opcode retrieves the currently selected namespace as a PMC object:</p>
1507		---
1508		> X<NameSpace PMC>
1509		> Namespaces are just PMCs. They implement the standard vtable functions
1510		> and a few extra methods. The C<get_namespace>X<get_namespace opcode>
1511		> opcode retrieves the currently selected namespace as a PMC object:
1512		>
1513		> $P0 = get_namespace
1514		1096d1239
1515		< <pre> $P0 = get_namespace</pre>
1516		1098,1102c1241,1244
1517		< <p>The <code>get_root_namespace</code><!--
1518		< INDEX: get_root_namespace opcode
1519		< --> opcode retrieves the namespace object for the root namespace. The <code>get_hll_namespace</code><!--
1520		< INDEX: get_hll_namespace opcode
1521		< --> opcode retrieves the virtual root for the currently selected HLL.</p>
1522		---
1523		> The C<get_root_namespace>X<get_root_namespace opcode> opcode retrieves
1524		> the namespace object for the root namespace. The
1525		> C<get_hll_namespace>X<get_hll_namespace opcode> opcode retrieves the
1526		> virtual root for the currently selected HLL.
1527		1104,1105c1246,1247
1528		< <pre> $P0 = get_root_namespace
1529		< $P0 = get_hll_namespace</pre>
1530		---
1531		> $P0 = get_root_namespace
1532		> $P0 = get_hll_namespace
1533		1107d1248
1534		< <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>
1535		1109,1111c1250,1251
1536		< <pre> $P0 = get_namespace ["Duck"]
1537		< $P0 = get_root_namespace ["General";"Electric"]
1538		< $P0 = get_hll_namespace ["Euro"]</pre>
1539		---
1540		> Each of these three opcodes can take a key argument to retrieve a namespace
1541		> under the currenly selected namespace, root namespace, or HLL root namespace:
1542		1113c1253,1255
1543		< <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>
1544		---
1545		> $P0 = get_namespace ["Duck"]
1546		> $P0 = get_root_namespace ["General";"Electric"]
1547		> $P0 = get_hll_namespace ["Euro"]
1548		1115,1116d1256
1549		< <pre> $P0 = get_hll_namespace ["Euro"]
1550		< $P1 = get_global $P0, "bill"</pre>
1551		1118,1120c1258,1261
1552		< <p>Namespaces also provide a set of methods to provide more complex behavior than the standard vtable functions allow. The <code>get_name</code><!--
1553		< INDEX: get_name method
1554		< --> method returns the name of the namespace as a <code>ResizableStringArray</code>:</p>
1555		---
1556		> Once you have a namespace object you can use it to retrieve variables from the
1557		> namespace instead of using a keyed lookup. This example first looks up the Euro
1558		> namespace in the currently selected HLL, then retrieves the C<bill> variable
1559		> from that namespace:
1560		1122c1263,1264
1561		< <pre> $P3 = $P0.'get_name'()</pre>
1562		---
1563		> $P0 = get_hll_namespace ["Euro"]
1564		> $P1 = get_global $P0, "bill"
1565		1124,1126d1265
1566		< <p>The <code>get_parent</code><!--
1567		< INDEX: get_parent method
1568		< --> method retrieves a namespace object for the parent namespace that contains this one:</p>
1569		1128c1267,1270
1570		< <pre> $P5 = $P0.'get_parent'()</pre>
1571		---
1572		> Namespaces also provide a set of methods to provide more complex
1573		> behavior than the standard vtable functions allow. The
1574		> C<get_name>X<get_name method> method returns the name of the namespace
1575		> as a C<ResizableStringArray>:
1576		1130,1132c1272
1577		< <p>The <code>get_class</code><!--
1578		< INDEX: get_class method
1579		< --> method retrieves any Class PMC associated with the namespace:</p>
1580		---
1581		> $P3 = $P0.'get_name'()
1582		1134d1273
1583		< <pre> $P6 = $P0.'get_class'()</pre>
1584		1136,1140c1275,1276
1585		< <p>The <code>add_var</code><!--
1586		< INDEX: add_var method
1587		< --> and <code>find_var</code><!--
1588		< INDEX: find_var method
1589		< --> methods store and retrieve variables in a namespace in a language-neutral way:</p>
1590		---
1591		> The C<get_parent>X<get_parent method> method retrieves a namespace
1592		> object for the parent namespace that contains this one:
1593		1142,1143c1278
1594		< <pre> $P0.'add_var'("bee", $P3)
1595		< $P1 = $P0.'find_var'("bee")</pre>
1596		---
1597		> $P5 = $P0.'get_parent'()
1598		1145,1147d1279
1599		< <p>The <code>find_namespace</code><!--
1600		< INDEX: find_namespace method
1601		< --> method looks up a namespace, just like the <code>get_namespace</code> opcode:</p>
1602		1149c1281,1282
1603		< <pre> $P1 = $P0.'find_namespace'("Duck")</pre>
1604		---
1605		> The C<get_class>X<get_class method> method retrieves any Class PMC
1606		> associated with the namespace:
1607		1151,1153c1284
1608		< <p>The <code>add_namespace</code><!--
1609		< INDEX: add_namespace method
1610		< --> method adds a new namespace as a child of the namespace object:</p>
1611		---
1612		> $P6 = $P0.'get_class'()
1613		1155d1285
1614		< <pre> $P0.'add_namespace'($P1)</pre>
1615		1157,1159c1287,1312
1616		< <p>The <code>make_namespace</code><!--
1617		< INDEX: make_namespace method
1618		< --> method looks up a namespace as a child of the namespace object and returns it. If the requested namespace doesn't exist, <code>make_namespace</code> creates a new one and adds it under that name:</p>
1619		---
1620		> The C<add_var>X<add_var method> and C<find_var>X<find_var method>
1621		> methods store and retrieve variables in a namespace in a
1622		> language-neutral way:
1623		>
1624		> $P0.'add_var'("bee", $P3)
1625		> $P1 = $P0.'find_var'("bee")
1626		>
1627		>
1628		> The C<find_namespace>X<find_namespace method> method looks up a
1629		> namespace, just like the C<get_namespace> opcode:
1630		>
1631		> $P1 = $P0.'find_namespace'("Duck")
1632		>
1633		>
1634		> The C<add_namespace>X<add_namespace method> method adds a new namespace
1635		> as a child of the namespace object:
1636		>
1637		> $P0.'add_namespace'($P1)
1638		>
1639		>
1640		> The C<make_namespace>X<make_namespace method> method looks up a
1641		> namespace as a child of the namespace object and returns it. If the
1642		> requested namespace doesn't exist, C<make_namespace> creates a new one
1643		> and adds it under that name:
1644		>
1645		> $P1 = $P0.'make_namespace'("Duck")
1646		1161d1313
1647		< <pre> $P1 = $P0.'make_namespace'("Duck")</pre>
1648		1166,1168c1318,1322
1649		< <p><!--
1650		< INDEX: aliasing
1651		< --> 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>
1652		---
1653		> X<aliasing>
1654		> Just like regular assignment, the various operations to store a variable in a
1655		> namespace only store a pointer to the PMC. If you modify the local PMC after
1656		> storing in a namespace, those changes will also appear in the stored global. To
1657		> store a true copy of the PMC, C<clone> it before you store it.
1658		1170c1324,1325
1659		< <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>
1660		---
1661		> Leaving the global variable as an alias for a local variable has its advantages.
1662		> If you retrieve a stored global into a register and modify it:
1663		1174c1329,1346
1664		< <p>... you modify the value of the stored global, so you don't need to call <code>set_global</code> again.</p>
1665		---
1666		> ... you modify the value of the stored global, so you don't need to call
1667		> C<set_global> again.
1668		>
1669		> <h1><a name="POD_ERRORS"
1670		> >POD ERRORS</a></h1>
1671		>
1672		> <p>Hey!
1673		> <b>The above document had some coding errors,
1674		> which are explained below:</b></p>
1675		>
1676		> <dl>
1677		> <dt><a name="Around_line_123:"
1678		> >Around line 123:</a></dt>
1679		> Deleting unknown formatting code G<>
1680		> <dt><a name="Around_line_185:"
1681		> >Around line 185:</a></dt>
1682		> =end PIR_FRAGMENT_INVALID[ doesn't match =begin PIR_FRAGMENT_INVALID.
1683		> (Stack: =begin PIR_FRAGMENT_INVALID)</dl>
1684		1178c1350
1685		< Copyright © 2002-2009, Parrot Foundation.
1686		---
1687		> Copyright © 2002-2010, Parrot Foundation.
1688		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
1689		5c5
1690		< <title>Parrot - Control Structures</title>
1691		---
1692		> <title>Parrot - Untitled</title>
1693		7c7
1694		< href="../../../../resources/parrot.css"
1695		---
1696		> href="/parrot.css"
1697		17c17
1698		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
1699		---
1700		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1701		23c23
1702		< <a href="../../../../html/index.html">Home</a> » Control Structures
1703		---
1704		> Untitled
1705		298a299,308
1706		>
1707		> <h1><a name="POD_ERRORS"
1708		> >POD ERRORS</a></h1>
1709		>
1710		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
1711		>
1712		> <dl>
1713		> <dt><a name="Around_line_5:"
1714		> >Around line 5:</a></dt>
1715		> Deleting unknown formatting code N<></dl>
1716		302c312
1717		< Copyright © 2002-2009, Parrot Foundation.
1718		---
1719		> Copyright © 2002-2010, Parrot Foundation.
1720		diff -r parrot-trunk/docs/html/docs/book/pir/ch06_subroutines.pod.html parrot/docs/html/docs/book/pir/ch06_subroutines.pod.html
1721		5c5
1722		< <title>Parrot - Subroutines</title>
1723		---
1724		> <title>Parrot - Untitled</title>
1725		7c7
1726		< href="../../../../resources/parrot.css"
1727		---
1728		> href="/parrot.css"
1729		17c17
1730		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
1731		---
1732		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1733		23c23
1734		< <a href="../../../../html/index.html">Home</a> » Subroutines
1735		---
1736		> Untitled
	1421	> <p>The <code>set_hll_global</code><!--
	1422	> INDEX: set_hll_global opcode
	1423	> --> and <code>get_hll_global</code><!--
	1424	> INDEX: get_hll_global opcode
	1425	> --> 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>
	1426	1224c1082
	1427	< .HLL 'Dutch'
	1428	---
	1429	> <pre> .HLL 'Dutch'
	1430	1226,1228c1084,1085
	1431	< set_hll_global ["Euro"], "bill", $P0
	1432	< $P1 = get_hll_global ["Euro"], "bill"
	1433	<
	1434	---
	1435	> set_hll_global ["Euro"], "bill", $P0
	1436	> $P1 = get_hll_global ["Euro"], "bill"</pre>
	1437	1233,1265c1090,1094
	1438	< X<NameSpace PMC>
	1439	< Namespaces are just PMCs. They implement the standard vtable functions
	1440	< and a few extra methods. The C<get_namespace>X<get_namespace opcode>
	1441	< opcode retrieves the currently selected namespace as a PMC object:
	1442	<
	1443	< $P0 = get_namespace
	1444	<
	1445	<
	1446	< The C<get_root_namespace>X<get_root_namespace opcode> opcode retrieves
	1447	< the namespace object for the root namespace. The
	1448	< C<get_hll_namespace>X<get_hll_namespace opcode> opcode retrieves the
	1449	< virtual root for the currently selected HLL.
	1450	<
	1451	< $P0 = get_root_namespace
	1452	< $P0 = get_hll_namespace
	1453	<
	1454	<
	1455	< Each of these three opcodes can take a key argument to retrieve a namespace
	1456	< under the currenly selected namespace, root namespace, or HLL root namespace:
	1457	<
	1458	< $P0 = get_namespace ["Duck"]
	1459	< $P0 = get_root_namespace ["General";"Electric"]
	1460	< $P0 = get_hll_namespace ["Euro"]
	1461	<
	1462	<
	1463	< Once you have a namespace object you can use it to retrieve variables from the
	1464	< namespace instead of using a keyed lookup. This example first looks up the Euro
	1465	< namespace in the currently selected HLL, then retrieves the C<bill> variable
	1466	< from that namespace:
	1467	<
	1468	< $P0 = get_hll_namespace ["Euro"]
	1469	< $P1 = get_global $P0, "bill"
	1470	<
	1471	---
	1472	> <p><!--
	1473	> INDEX: NameSpace PMC
	1474	> --> Namespaces are just PMCs. They implement the standard vtable functions and a few extra methods. The <code>get_namespace</code><!--
	1475	> INDEX: get_namespace opcode
	1476	> --> opcode retrieves the currently selected namespace as a PMC object:</p>
	1477	1267,1270c1096
	1478	< Namespaces also provide a set of methods to provide more complex
	1479	< behavior than the standard vtable functions allow. The
	1480	< C<get_name>X<get_name method> method returns the name of the namespace
	1481	< as a C<ResizableStringArray>:
	1482	---
	1483	> <pre> $P0 = get_namespace</pre>
	1484	1272c1098,1102
	1485	< $P3 = $P0.'get_name'()
	1486	---
	1487	> <p>The <code>get_root_namespace</code><!--
	1488	> INDEX: get_root_namespace opcode
	1489	> --> opcode retrieves the namespace object for the root namespace. The <code>get_hll_namespace</code><!--
	1490	> INDEX: get_hll_namespace opcode
	1491	> --> opcode retrieves the virtual root for the currently selected HLL.</p>
	1492	1273a1104,1105
	1493	> <pre> $P0 = get_root_namespace
	1494	> $P0 = get_hll_namespace</pre>
	1495	1275,1276c1107
	1496	< The C<get_parent>X<get_parent method> method retrieves a namespace
	1497	< object for the parent namespace that contains this one:
	1498	---
	1499	> <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>
	1500	1278c1109,1111
	1501	< $P5 = $P0.'get_parent'()
	1502	---
	1503	> <pre> $P0 = get_namespace ["Duck"]
	1504	> $P0 = get_root_namespace ["General";"Electric"]
	1505	> $P0 = get_hll_namespace ["Euro"]</pre>
	1506	1279a1113
	1507	> <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>
	1508	1281,1282c1115,1116
	1509	< The C<get_class>X<get_class method> method retrieves any Class PMC
	1510	< associated with the namespace:
	1511	---
	1512	> <pre> $P0 = get_hll_namespace ["Euro"]
	1513	> $P1 = get_global $P0, "bill"</pre>
	1514	1284c1118,1120
	1515	< $P6 = $P0.'get_class'()
	1516	---
	1517	> <p>Namespaces also provide a set of methods to provide more complex behavior than the standard vtable functions allow. The <code>get_name</code><!--
	1518	> INDEX: get_name method
	1519	> --> method returns the name of the namespace as a <code>ResizableStringArray</code>:</p>
	1520	1285a1122
	1521	> <pre> $P3 = $P0.'get_name'()</pre>
	1522	1287,1289c1124,1126
	1523	< The C<add_var>X<add_var method> and C<find_var>X<find_var method>
	1524	< methods store and retrieve variables in a namespace in a
	1525	< language-neutral way:
	1526	---
	1527	> <p>The <code>get_parent</code><!--
	1528	> INDEX: get_parent method
	1529	> --> method retrieves a namespace object for the parent namespace that contains this one:</p>
	1530	1291,1292c1128
	1531	< $P0.'add_var'("bee", $P3)
	1532	< $P1 = $P0.'find_var'("bee")
	1533	---
	1534	> <pre> $P5 = $P0.'get_parent'()</pre>
	1535	1293a1130,1132
	1536	> <p>The <code>get_class</code><!--
	1537	> INDEX: get_class method
	1538	> --> method retrieves any Class PMC associated with the namespace:</p>
	1539	1295,1296c1134
	1540	< The C<find_namespace>X<find_namespace method> method looks up a
	1541	< namespace, just like the C<get_namespace> opcode:
	1542	---
	1543	> <pre> $P6 = $P0.'get_class'()</pre>
	1544	1298c1136,1140
	1545	< $P1 = $P0.'find_namespace'("Duck")
	1546	---
	1547	> <p>The <code>add_var</code><!--
	1548	> INDEX: add_var method
	1549	> --> and <code>find_var</code><!--
	1550	> INDEX: find_var method
	1551	> --> methods store and retrieve variables in a namespace in a language-neutral way:</p>
	1552	1299a1142,1143
	1553	> <pre> $P0.'add_var'("bee", $P3)
	1554	> $P1 = $P0.'find_var'("bee")</pre>
	1555	1301,1302c1145,1147
	1556	< The C<add_namespace>X<add_namespace method> method adds a new namespace
	1557	< as a child of the namespace object:
	1558	---
	1559	> <p>The <code>find_namespace</code><!--
	1560	> INDEX: find_namespace method
	1561	> --> method looks up a namespace, just like the <code>get_namespace</code> opcode:</p>
	1562	1304c1149
	1563	< $P0.'add_namespace'($P1)
	1564	---
	1565	> <pre> $P1 = $P0.'find_namespace'("Duck")</pre>
	1566	1305a1151,1153
	1567	> <p>The <code>add_namespace</code><!--
	1568	> INDEX: add_namespace method
	1569	> --> method adds a new namespace as a child of the namespace object:</p>
	1570	1307,1310c1155
	1571	< The C<make_namespace>X<make_namespace method> method looks up a
	1572	< namespace as a child of the namespace object and returns it. If the
	1573	< requested namespace doesn't exist, C<make_namespace> creates a new one
	1574	< and adds it under that name:
	1575	---
	1576	> <pre> $P0.'add_namespace'($P1)</pre>
	1577	1312c1157,1159
	1578	< $P1 = $P0.'make_namespace'("Duck")
	1579	---
	1580	> <p>The <code>make_namespace</code><!--
	1581	> INDEX: make_namespace method
	1582	> --> method looks up a namespace as a child of the namespace object and returns it. If the requested namespace doesn't exist, <code>make_namespace</code> creates a new one and adds it under that name:</p>
	1583	1313a1161
	1584	> <pre> $P1 = $P0.'make_namespace'("Duck")</pre>
	1585	1318,1322c1166,1168
	1586	< X<aliasing>
	1587	< Just like regular assignment, the various operations to store a variable in a
	1588	< namespace only store a pointer to the PMC. If you modify the local PMC after
	1589	< storing in a namespace, those changes will also appear in the stored global. To
	1590	< store a true copy of the PMC, C<clone> it before you store it.
	1591	---
	1592	> <p><!--
	1593	> INDEX: aliasing
	1594	> --> 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>
	1595	1324,1325c1170
	1596	< Leaving the global variable as an alias for a local variable has its advantages.
	1597	< If you retrieve a stored global into a register and modify it:
	1598	---
	1599	> <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>
	1600	1329,1346c1174
	1601	< ... you modify the value of the stored global, so you don't need to call
	1602	< C<set_global> again.
	1603	<
	1604	< <h1><a name="POD_ERRORS"
	1605	< >POD ERRORS</a></h1>
	1606	<
	1607	< <p>Hey!
	1608	< <b>The above document had some coding errors,
	1609	< which are explained below:</b></p>
	1610	<
	1611	< <dl>
	1612	< <dt><a name="Around_line_123:"
	1613	< >Around line 123:</a></dt>
	1614	< Deleting unknown formatting code G<>
	1615	< <dt><a name="Around_line_185:"
	1616	< >Around line 185:</a></dt>
	1617	< =end PIR_FRAGMENT_INVALID[ doesn't match =begin PIR_FRAGMENT_INVALID.
	1618	< (Stack: =begin PIR_FRAGMENT_INVALID)</dl>
	1619	---
	1620	> <p>... you modify the value of the stored global, so you don't need to call <code>set_global</code> again.</p>
	1621	1350c1178
	1622	< Copyright © 2002-2010, Parrot Foundation.
	1623	---
	1624	> Copyright © 2002-2009, Parrot Foundation.
	1625	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
	1626	5c5
	1627	< <title>Parrot - Untitled</title>
	1628	---
	1629	> <title>Parrot - Control Structures</title>
	1630	23c23
	1631	< Untitled
	1632	---
	1633	> <a href="../../../../html/index.html">Home</a> » Control Structures
	1634	299,308d298
	1635	<
	1636	< <h1><a name="POD_ERRORS"
	1637	< >POD ERRORS</a></h1>
	1638	<
	1639	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	1640	<
	1641	< <dl>
	1642	< <dt><a name="Around_line_5:"
	1643	< >Around line 5:</a></dt>
	1644	< Deleting unknown formatting code N<></dl>
	1645	312c302
	1646	< Copyright © 2002-2010, Parrot Foundation.
	1647	---
	1648	> Copyright © 2002-2009, Parrot Foundation.
	1649	diff -r parrot/docs/html/docs/book/pir/ch06_subroutines.pod.html parrot-trunk/docs/html/docs/book/pir/ch06_subroutines.pod.html
	1650	5c5
	1651	< <title>Parrot - Untitled</title>
	1652	---
	1653	> <title>Parrot - Subroutines</title>
	1654	23c23
	1655	< Untitled
	1656	---
	1657	> <a href="../../../../html/index.html">Home</a> » Subroutines
1737	1658	759c759
1738		< --> 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>
1739		---
1740		> --> 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>
1741		785a786,807
1742		>
1743		> <h1><a name="POD_ERRORS"
1744		> >POD ERRORS</a></h1>
1745		>
1746		> <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
1747		>
1748		> <dl>
1749		> <dt><a name="Around_line_39:"
1750		> >Around line 39:</a></dt>
1751		> Deleting unknown formatting code N<>
1752		> <dt><a name="Around_line_393:"
1753		> >Around line 393:</a></dt>
1754		> Deleting unknown formatting code N<>
1755		> <dt><a name="Around_line_615:"
1756		> >Around line 615:</a></dt>
1757		> Deleting unknown formatting code N<>
1758		> <dt><a name="Around_line_625:"
1759		> >Around line 625:</a></dt>
1760		> Deleting unknown formatting code N<>
1761		> <dt><a name="Around_line_1083:"
1762		> >Around line 1083:</a></dt>
1763		> Deleting unknown formatting code N<></dl>
1764		789c811
1765		< Copyright © 2002-2009, Parrot Foundation.
1766		---
1767		> Copyright © 2002-2010, Parrot Foundation.
1768		diff -r parrot-trunk/docs/html/docs/book/pir/ch07_objects.pod.html parrot/docs/html/docs/book/pir/ch07_objects.pod.html
1769		5c5
1770		< <title>Parrot - Classes and Objects</title>
1771		---
1772		> <title>Parrot - Untitled</title>
1773		7c7
1774		< href="../../../../resources/parrot.css"
1775		---
1776		> href="/parrot.css"
1777		17c17
1778		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
1779		---
1780		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1781		23c23
1782		< <a href="../../../../html/index.html">Home</a> » Classes and Objects
1783		---
1784		> Untitled
1785		337a338,349
1786		>
1787		> <h1><a name="POD_ERRORS"
1788		> >POD ERRORS</a></h1>
1789		>
1790		> <p>Hey!
1791		> <b>The above document had some coding errors,
1792		> which are explained below:</b></p>
1793		>
1794		> <dl>
1795		> <dt><a name="Around_line_64:"
1796		> >Around line 64:</a></dt>
1797		> Deleting unknown formatting code N<></dl>
1798		341c353
1799		< Copyright © 2002-2009, Parrot Foundation.
1800		---
1801		> Copyright © 2002-2010, Parrot Foundation.
1802		diff -r parrot-trunk/docs/html/docs/book/pir/ch08_io.pod.html parrot/docs/html/docs/book/pir/ch08_io.pod.html
1803		5c5
1804		< <title>Parrot - I/O</title>
1805		---
1806		> <title>Parrot - Untitled</title>
1807		7c7
1808		< href="../../../../resources/parrot.css"
1809		---
1810		> href="/parrot.css"
1811		17c17
1812		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
1813		---
1814		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1815		23c23
1816		< <a href="../../../../html/index.html">Home</a> » I/O
1817		---
1818		> Untitled
1819		365c365,380
1820		< </pre> </div> <!-- "mainbody" -->
1821		---
1822		> </pre>
1823		> <h1><a name="POD_ERRORS"
1824		> >POD ERRORS</a></h1>
1825		>
1826		> <p>Hey!
1827		> <b>The above document had some coding errors,
1828		> which are explained below:</b></p>
1829		>
1830		> <dl>
1831		> <dt><a name="Around_line_25:"
1832		> >Around line 25:</a></dt>
1833		> Deleting unknown formatting code N<>
1834		> <dt><a name="Around_line_46:"
1835		> >Around line 46:</a></dt>
1836		> Deleting unknown formatting code N<></dl>
1837		> </div> <!-- "mainbody" -->
1838		368c383
1839		< Copyright © 2002-2009, Parrot Foundation.
1840		---
1841		> Copyright © 2002-2010, Parrot Foundation.
1842		diff -r parrot-trunk/docs/html/docs/book/pir/ch09_exceptions.pod.html parrot/docs/html/docs/book/pir/ch09_exceptions.pod.html
1843		5c5
1844		< <title>Parrot - Exceptions</title>
1845		---
1846		> <title>Parrot - Untitled</title>
1847		7c7
1848		< href="../../../../resources/parrot.css"
1849		---
1850		> href="/parrot.css"
1851		17c17
1852		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
1853		---
1854		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1855		23c23
1856		< <a href="../../../../html/index.html">Home</a> » Exceptions
1857		---
1858		> Untitled
	1659	< --> 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>
	1660	---
	1661	> --> 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>
	1662	786,807d785
	1663	<
	1664	< <h1><a name="POD_ERRORS"
	1665	< >POD ERRORS</a></h1>
	1666	<
	1667	< <p>Hey! <b>The above document had some coding errors, which are explained below:</b></p>
	1668	<
	1669	< <dl>
	1670	< <dt><a name="Around_line_39:"
	1671	< >Around line 39:</a></dt>
	1672	< Deleting unknown formatting code N<>
	1673	< <dt><a name="Around_line_393:"
	1674	< >Around line 393:</a></dt>
	1675	< Deleting unknown formatting code N<>
	1676	< <dt><a name="Around_line_615:"
	1677	< >Around line 615:</a></dt>
	1678	< Deleting unknown formatting code N<>
	1679	< <dt><a name="Around_line_625:"
	1680	< >Around line 625:</a></dt>
	1681	< Deleting unknown formatting code N<>
	1682	< <dt><a name="Around_line_1083:"
	1683	< >Around line 1083:</a></dt>
	1684	< Deleting unknown formatting code N<></dl>
	1685	811c789
	1686	< Copyright © 2002-2010, Parrot Foundation.
	1687	---
	1688	> Copyright © 2002-2009, Parrot Foundation.
	1689	diff -r parrot/docs/html/docs/book/pir/ch07_objects.pod.html parrot-trunk/docs/html/docs/book/pir/ch07_objects.pod.html
	1690	5c5
	1691	< <title>Parrot - Untitled</title>
	1692	---
	1693	> <title>Parrot - Classes and Objects</title>
	1694	23c23
	1695	< Untitled
	1696	---
	1697	> <a href="../../../../html/index.html">Home</a> » Classes and Objects
	1698	338,349d337
	1699	<
	1700	< <h1><a name="POD_ERRORS"
	1701	< >POD ERRORS</a></h1>
	1702	<
	1703	< <p>Hey!
	1704	< <b>The above document had some coding errors,
	1705	< which are explained below:</b></p>
	1706	<
	1707	< <dl>
	1708	< <dt><a name="Around_line_64:"
	1709	< >Around line 64:</a></dt>
	1710	< Deleting unknown formatting code N<></dl>
	1711	353c341
	1712	< Copyright © 2002-2010, Parrot Foundation.
	1713	---
	1714	> Copyright © 2002-2009, Parrot Foundation.
	1715	diff -r parrot/docs/html/docs/book/pir/ch08_io.pod.html parrot-trunk/docs/html/docs/book/pir/ch08_io.pod.html
	1716	5c5
	1717	< <title>Parrot - Untitled</title>
	1718	---
	1719	> <title>Parrot - I/O</title>
	1720	23c23
	1721	< Untitled
	1722	---
	1723	> <a href="../../../../html/index.html">Home</a> » I/O
	1724	365,380c365
	1725	< </pre>
	1726	< <h1><a name="POD_ERRORS"
	1727	< >POD ERRORS</a></h1>
	1728	<
	1729	< <p>Hey!
	1730	< <b>The above document had some coding errors,
	1731	< which are explained below:</b></p>
	1732	<
	1733	< <dl>
	1734	< <dt><a name="Around_line_25:"
	1735	< >Around line 25:</a></dt>
	1736	< Deleting unknown formatting code N<>
	1737	< <dt><a name="Around_line_46:"
	1738	< >Around line 46:</a></dt>
	1739	< Deleting unknown formatting code N<></dl>
	1740	< </div> <!-- "mainbody" -->
	1741	---
	1742	> </pre> </div> <!-- "mainbody" -->
	1743	383c368
	1744	< Copyright © 2002-2010, Parrot Foundation.
	1745	---
	1746	> Copyright © 2002-2009, Parrot Foundation.
	1747	diff -r parrot/docs/html/docs/book/pir/ch09_exceptions.pod.html parrot-trunk/docs/html/docs/book/pir/ch09_exceptions.pod.html
	1748	5c5
	1749	< <title>Parrot - Untitled</title>
	1750	---
	1751	> <title>Parrot - Exceptions</title>
	1752	23c23
	1753	< Untitled
	1754	---
	1755	> <a href="../../../../html/index.html">Home</a> » Exceptions
1859	1756	277c277
1860		< Copyright © 2002-2009, Parrot Foundation.
1861		---
1862		> Copyright © 2002-2010, Parrot Foundation.
1863		diff -r parrot-trunk/docs/html/docs/compiler_faq.pod.html parrot/docs/html/docs/compiler_faq.pod.html
1864		5c5
1865		< <title>Parrot - Parrot FAQ for compiler writers in PIR</title>
1866		---
1867		> <title>Parrot - Untitled</title>
1868		7c7
1869		< href="../../resources/parrot.css"
1870		---
1871		> href="/parrot.css"
1872		17c17
1873		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
1874		---
1875		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1876		23c23
1877		< <a href="../../html/index.html">Home</a> » Parrot FAQ for compiler writers in PIR
1878		---
1879		> Untitled
	1757	< Copyright © 2002-2010, Parrot Foundation.
	1758	---
	1759	> Copyright © 2002-2009, Parrot Foundation.
	1760	diff -r parrot/docs/html/docs/compiler_faq.pod.html parrot-trunk/docs/html/docs/compiler_faq.pod.html
	1761	5c5
	1762	< <title>Parrot - Untitled</title>
	1763	---
	1764	> <title>Parrot - Parrot FAQ for compiler writers in PIR</title>
	1765	23c23
	1766	< Untitled
	1767	---
	1768	> <a href="../../html/index.html">Home</a> » Parrot FAQ for compiler writers in PIR
1880	1769	302c302
1881		< See also <em>~~<a href="../t/dynpmc/dynlexpad.t.html">t/dynpmc/dynlexpad.t</a>~~</em>.</p>
1882		---
1883		> See also <em>~~t/dynpmc/dynlexpad.t~~</em>.</p>
	1770	< See also <em>t/dynpmc/dynlexpad.t</em>.</p>
	1771	---
	1772	> See also <em><a href="../t/dynpmc/dynlexpad.t.html">t/dynpmc/dynlexpad.t</a></em>.</p>
1884	1773	636c636
1885		< Copyright © 2002-2009, Parrot Foundation.
1886		---
1887		> Copyright © 2002-2010, Parrot Foundation.
1888		diff -r parrot-trunk/docs/html/docs/configuration.pod.html parrot/docs/html/docs/configuration.pod.html
1889		5c5
1890		< <title>Parrot - Parrot Configuration System</title>
1891		---
1892		> <title>Parrot - Untitled</title>
1893		7c7
1894		< href="../../resources/parrot.css"
1895		---
1896		> href="/parrot.css"
1897		17c17
1898		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
1899		---
1900		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1901		23c23
1902		< <a href="../../html/index.html">Home</a> » <a href="../../html/tools.html">Tools</a> » Parrot Configuration System
1903		---
1904		> Untitled
	1774	< Copyright © 2002-2010, Parrot Foundation.
	1775	---
	1776	> Copyright © 2002-2009, Parrot Foundation.
	1777	diff -r parrot/docs/html/docs/configuration.pod.html parrot-trunk/docs/html/docs/configuration.pod.html
	1778	5c5
	1779	< <title>Parrot - Untitled</title>
	1780	---
	1781	> <title>Parrot - Parrot Configuration System</title>
	1782	23c23
	1783	< Untitled
	1784	---
	1785	> <a href="../../html/index.html">Home</a> » <a href="../../html/tools.html">Tools</a> » Parrot Configuration System
1905	1786	55c55
1906		< 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>.
1907		---
1908		> you would add the code used to determine its size in <em>~~config/auto/sizes.pm~~</em>.
	1787	< you would add the code used to determine its size in <em>config/auto/sizes.pm</em>.
	1788	---
	1789	> 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>.
1909	1790	83c83
1910		< To enable them run <em>~~<a href="../Configure.pl.html">Configure.pl</a>~~</em> with the <code>--ask</code> option.</p>
1911		---
1912		> To enable them run <em>~~Configure.pl~~</em> with the <code>--ask</code> option.</p>
	1791	< To enable them run <em>Configure.pl</em> with the <code>--ask</code> option.</p>
	1792	---
	1793	> To enable them run <em><a href="../Configure.pl.html">Configure.pl</a></em> with the <code>--ask</code> option.</p>
1913	1794	118,119c118,119
1914		< the <em>~~<a href="../Configure.pl.html">Configure.pl</a>~~</em> script.
1915		< The system is invoked by instantiating a <a href='~~..%2Flib%2FParrot%2FConfigure.pm.html~~'>Parrot::Configure</a> object,
1916		---
1917		> the <em>~~Configure.pl~~</em> script.
1918		> The system is invoked by instantiating a <a href='~~TODO~~'>Parrot::Configure</a> object,
	1795	< the <em>Configure.pl</em> script.
	1796	< The system is invoked by instantiating a <a href='TODO'>Parrot::Configure</a> object,
	1797	---
	1798	> the <em><a href="../Configure.pl.html">Configure.pl</a></em> script.
	1799	> The system is invoked by instantiating a <a href='..%2Flib%2FParrot%2FConfigure.pm.html'>Parrot::Configure</a> object,
1919	1800	131c131
1920		< the step <em>~~<a href="../config/init/defaults.pm.html">config/init/defaults.pm</a>~~</em> uses the <code>init::defaults</code> namespace.</p>
1921		---
1922		> the step <em>~~config/init/defaults.pm~~</em> uses the <code>init::defaults</code> namespace.</p>
	1801	< the step <em>config/init/defaults.pm</em> uses the <code>init::defaults</code> namespace.</p>
	1802	---
	1803	> the step <em><a href="../config/init/defaults.pm.html">config/init/defaults.pm</a></em> uses the <code>init::defaults</code> namespace.</p>
1923	1804	133c133
1924		< <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>.
1925		---
1926		> <p>Each step inherits its constructor and some other methods from <em>~~lib/Parrot/Configure/Step.pm~~</em>.
	1805	< <p>Each step inherits its constructor and some other methods from <em>lib/Parrot/Configure/Step.pm</em>.
	1806	---
	1807	> <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>.
1927	1808	167c167
1928		< <p>The configuration system won't execute your step by default unless it'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>
1929		---
1930		> <p>The configuration system won't execute your step by default unless it'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>
	1809	< <p>The configuration system won't execute your step by default unless it'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>
	1810	---
	1811	> <p>The configuration system won't execute your step by default unless it'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>
1931	1812	169c169
1932		< <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>
1933		---
1934		> <p>Various utility functions for configuration steps are provided by the <a href='~~TODO~~'>Parrot::Configure::Utils</a> module.</p>
	1813	< <p>Various utility functions for configuration steps are provided by the <a href='TODO'>Parrot::Configure::Utils</a> module.</p>
	1814	---
	1815	> <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>
1935	1816	210c210
1936		< <p>Command-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'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>
1937		---
1938		> <p>Command-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'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>
	1817	< <p>Command-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'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>
	1818	---
	1819	> <p>Command-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'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>
1939	1820	212c212
1940		< <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>
1941		---
1942		> <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>
	1821	< <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>
	1822	---
	1823	> <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>
1943	1824	217c217
1944		< <p>As an alternative to typing a long string of options on the command-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>
1945		---
1946		> <p>As an alternative to typing a long string of options on the command-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>
	1825	< <p>As an alternative to typing a long string of options on the command-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>
	1826	---
	1827	> <p>As an alternative to typing a long string of options on the command-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>
1947	1828	228c228
1948		< <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's data by interacting with this object. Some of its methods are summarized below.</p>
1949		---
1950		> <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's data by interacting with this object. Some of its methods are summarized below.</p>
	1829	< <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's data by interacting with this object. Some of its methods are summarized below.</p>
	1830	---
	1831	> <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's data by interacting with this object. Some of its methods are summarized below.</p>
1951	1832	245c245
1952		< Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system's data.See the <a href='~~..%2Flib%2FParrot%2FConfigure%2FData.pm.html~~'>Parrot::Configure::Data</a> documentation for further details.</dl>
1953		---
1954		> Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system's data.See the <a href='~~TODO~~'>Parrot::Configure::Data</a> documentation for further details.</dl>
	1833	< Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system's data.See the <a href='TODO'>Parrot::Configure::Data</a> documentation for further details.</dl>
	1834	---
	1835	> Returns a string that can be <code>eval</code>ed by Perl to create a hash representing the configuration system's data.See the <a href='..%2Flib%2FParrot%2FConfigure%2FData.pm.html'>Parrot::Configure::Data</a> documentation for further details.</dl>
1955	1836	261c261
1956		< 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>
1957		---
1958		> These settings are deleted before <em>~~lib/Parrot/Config.pm~~</em> is written. These entries are only used e.g. for Makefile creation.</dl>
	1837	< These settings are deleted before <em>lib/Parrot/Config.pm</em> is written. These entries are only used e.g. for Makefile creation.</dl>
	1838	---
	1839	> 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>
1959	1840	266c266
1960		< <p>Parrot configuration is currently jump-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>
1961		---
1962		> <p>Parrot configuration is currently jump-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>
	1841	< <p>Parrot configuration is currently jump-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>
	1842	---
	1843	> <p>Parrot configuration is currently jump-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>
1963	1844	276c276
1964		< <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>
1965		---
1966		> <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>
	1845	< <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>
	1846	---
	1847	> <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>
1967	1848	280c280
1968		< Copyright © 2002-2009, Parrot Foundation.
1969		---
1970		> Copyright © 2002-2010, Parrot Foundation.
1971		diff -r parrot-trunk/docs/html/docs/debugger.pod.html parrot/docs/html/docs/debugger.pod.html
1972		5c5
1973		< <title>Parrot - The Parrot Debugger</title>
1974		---
1975		> <title>Parrot - Untitled</title>
1976		7c7
1977		< href="../../resources/parrot.css"
1978		---
1979		> href="/parrot.css"
1980		17c17
1981		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
1982		---
1983		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
1984		23c23
1985		< <a href="../../html/index.html">Home</a> » <a href="../../html/tools.html">Tools</a> » The Parrot Debugger
1986		---
1987		> Untitled
	1849	< Copyright © 2002-2010, Parrot Foundation.
	1850	---
	1851	> Copyright © 2002-2009, Parrot Foundation.
	1852	diff -r parrot/docs/html/docs/debugger.pod.html parrot-trunk/docs/html/docs/debugger.pod.html
	1853	5c5
	1854	< <title>Parrot - Untitled</title>
	1855	---
	1856	> <title>Parrot - The Parrot Debugger</title>
	1857	23c23
	1858	< Untitled
	1859	---
	1860	> <a href="../../html/index.html">Home</a> » <a href="../../html/tools.html">Tools</a> » The Parrot Debugger
1988	1861	307c307
1989		< Copyright © 2002-2009, Parrot Foundation.
1990		---
1991		> Copyright © 2002-2010, Parrot Foundation.
1992		diff -r parrot-trunk/docs/html/docs/debug.pod.html parrot/docs/html/docs/debug.pod.html
1993		5c5
1994		< <title>Parrot - Debugging Parrot</title>
1995		---
1996		> <title>Parrot - Untitled</title>
1997		7c7
1998		< href="../../resources/parrot.css"
1999		---
2000		> href="/parrot.css"
2001		17c17
2002		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2003		---
2004		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2005		23c23
2006		< <a href="../../html/index.html">Home</a> » <a href="../../html/tools.html">Tools</a> » Debugging Parrot
2007		---
2008		> Untitled
	1862	< Copyright © 2002-2010, Parrot Foundation.
	1863	---
	1864	> Copyright © 2002-2009, Parrot Foundation.
	1865	diff -r parrot/docs/html/docs/debug.pod.html parrot-trunk/docs/html/docs/debug.pod.html
	1866	5c5
	1867	< <title>Parrot - Untitled</title>
	1868	---
	1869	> <title>Parrot - Debugging Parrot</title>
	1870	23c23
	1871	< Untitled
	1872	---
	1873	> <a href="../../html/index.html">Home</a> » <a href="../../html/tools.html">Tools</a> » Debugging Parrot
2009	1874	76c76
2010		< <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>
2011		---
2012		> <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>
	1875	< <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>
	1876	---
	1877	> <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>
2013	1878	88c88
2014		< <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>
2015		---
2016		> <p>One possible tool is <code>parrot_debugger</code>, the Parrot Debugger. See <em>~~docs/debugger.pod~~</em> for details on it.</p>
	1879	< <p>One possible tool is <code>parrot_debugger</code>, the Parrot Debugger. See <em>docs/debugger.pod</em> for details on it.</p>
	1880	---
	1881	> <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>
2017	1882	247c247
2018		< Copyright © 2002-2009, Parrot Foundation.
2019		---
2020		> Copyright © 2002-2010, Parrot Foundation.
2021		diff -r parrot-trunk/docs/html/docs/dev/byteorder.pod.html parrot/docs/html/docs/dev/byteorder.pod.html
2022		5c5
2023		< <title>Parrot - Byteorder Conversion Functions</title>
2024		---
2025		> <title>Parrot - Untitled</title>
2026		7c7
2027		< href="../../../resources/parrot.css"
2028		---
2029		> href="/parrot.css"
2030		17c17
2031		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2032		---
2033		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2034		23c23
2035		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Byteorder Conversion Functions
2036		---
2037		> Untitled
	1883	< Copyright © 2002-2010, Parrot Foundation.
	1884	---
	1885	> Copyright © 2002-2009, Parrot Foundation.
	1886	diff -r parrot/docs/html/docs/dev/byteorder.pod.html parrot-trunk/docs/html/docs/dev/byteorder.pod.html
	1887	5c5
	1888	< <title>Parrot - Untitled</title>
	1889	---
	1890	> <title>Parrot - Byteorder Conversion Functions</title>
	1891	23c23
	1892	< Untitled
	1893	---
	1894	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Byteorder Conversion Functions
2038	1895	54c54
2039		< <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>
2040		---
2041		> <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>
	1896	< <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>
	1897	---
	1898	> <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>
2042	1899	129c129
2043		< <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>
2044		---
2045		> <p>The fetch and transformer functions are implemented in <em>~~src/packfile/pf_items.c~~</em></p>
	1900	< <p>The fetch and transformer functions are implemented in <em>src/packfile/pf_items.c</em></p>
	1901	---
	1902	> <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>
2046	1903	133c133
2047		< Copyright © 2002-2009, Parrot Foundation.
2048		---
2049		> Copyright © 2002-2010, Parrot Foundation.
2050		diff -r parrot-trunk/docs/html/docs/dev/c_functions.pod.html parrot/docs/html/docs/dev/c_functions.pod.html
2051		5c5
2052		< <title>Parrot - C function decoration guidelines</title>
2053		---
2054		> <title>Parrot - Untitled</title>
2055		7c7
2056		< href="../../../resources/parrot.css"
2057		---
2058		> href="/parrot.css"
2059		17c17
2060		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2061		---
2062		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2063		23c23
2064		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » C function decoration guidelines
2065		---
2066		> Untitled
	1904	< Copyright © 2002-2010, Parrot Foundation.
	1905	---
	1906	> Copyright © 2002-2009, Parrot Foundation.
	1907	diff -r parrot/docs/html/docs/dev/c_functions.pod.html parrot-trunk/docs/html/docs/dev/c_functions.pod.html
	1908	5c5
	1909	< <title>Parrot - Untitled</title>
	1910	---
	1911	> <title>Parrot - C function decoration guidelines</title>
	1912	23c23
	1913	< Untitled
	1914	---
	1915	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » C function decoration guidelines
2067	1916	214c214
2068		< Copyright © 2002-2009, Parrot Foundation.
2069		---
2070		> Copyright © 2002-2010, Parrot Foundation.
2071		diff -r parrot-trunk/docs/html/docs/dev/debugging_with_msvc.pod.html parrot/docs/html/docs/dev/debugging_with_msvc.pod.html
2072		5c5
2073		< <title>Parrot - Debugging Parrot with Microsoft</title>
2074		---
2075		> <title>Parrot - Untitled</title>
2076		7c7
2077		< href="../../../resources/parrot.css"
2078		---
2079		> href="/parrot.css"
2080		17c17
2081		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2082		---
2083		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2084		23c23
2085		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Debugging Parrot with Microsoft
2086		---
2087		> Untitled
	1917	< Copyright © 2002-2010, Parrot Foundation.
	1918	---
	1919	> Copyright © 2002-2009, Parrot Foundation.
	1920	diff -r parrot/docs/html/docs/dev/debugging_with_msvc.pod.html parrot-trunk/docs/html/docs/dev/debugging_with_msvc.pod.html
	1921	5c5
	1922	< <title>Parrot - Untitled</title>
	1923	---
	1924	> <title>Parrot - Debugging Parrot with Microsoft</title>
	1925	23c23
	1926	< Untitled
	1927	---
	1928	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Debugging Parrot with Microsoft
2088	1929	161c161
2089		< Copyright © 2002-2009, Parrot Foundation.
2090		---
2091		> Copyright © 2002-2010, Parrot Foundation.
2092		diff -r parrot-trunk/docs/html/docs/dev/events.pod.html parrot/docs/html/docs/dev/events.pod.html
2093		5c5
2094		< <title>Parrot - Design Notes for Events</title>
2095		---
2096		> <title>Parrot - Untitled</title>
2097		7c7
2098		< href="../../../resources/parrot.css"
2099		---
2100		> href="/parrot.css"
2101		17c17
2102		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2103		---
2104		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2105		23c23
2106		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Design Notes for Events
2107		---
2108		> Untitled
	1930	< Copyright © 2002-2010, Parrot Foundation.
	1931	---
	1932	> Copyright © 2002-2009, Parrot Foundation.
	1933	diff -r parrot/docs/html/docs/dev/events.pod.html parrot-trunk/docs/html/docs/dev/events.pod.html
	1934	5c5
	1935	< <title>Parrot - Untitled</title>
	1936	---
	1937	> <title>Parrot - Design Notes for Events</title>
	1938	23c23
	1939	< Untitled
	1940	---
	1941	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Design Notes for Events
2109	1942	152c152
2110		< Copyright © 2002-2009, Parrot Foundation.
2111		---
2112		> Copyright © 2002-2010, Parrot Foundation.
2113		diff -r parrot-trunk/docs/html/docs/dev/headerizer.pod.html parrot/docs/html/docs/dev/headerizer.pod.html
2114		5c5
2115		< <title>Parrot - The Headerizer</title>
2116		---
2117		> <title>Parrot - Untitled</title>
2118		7c7
2119		< href="../../../resources/parrot.css"
2120		---
2121		> href="/parrot.css"
2122		17c17
2123		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2124		---
2125		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2126		23c23
2127		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » The Headerizer
2128		---
2129		> Untitled
	1943	< Copyright © 2002-2010, Parrot Foundation.
	1944	---
	1945	> Copyright © 2002-2009, Parrot Foundation.
	1946	diff -r parrot/docs/html/docs/dev/headerizer.pod.html parrot-trunk/docs/html/docs/dev/headerizer.pod.html
	1947	5c5
	1948	< <title>Parrot - Untitled</title>
	1949	---
	1950	> <title>Parrot - The Headerizer</title>
	1951	23c23
	1952	< Untitled
	1953	---
	1954	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » The Headerizer
2130	1955	39c39
2131		< <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>
2132		---
2133		> <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>
	1956	< <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>
	1957	---
	1958	> <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>
2134	1959	66c66
2135		< Copyright © 2002-2009, Parrot Foundation.
2136		---
2137		> Copyright © 2002-2010, Parrot Foundation.
2138		diff -r parrot-trunk/docs/html/docs/dev/infant.pod.html parrot/docs/html/docs/dev/infant.pod.html
2139		5c5
2140		< <title>Parrot - Infant Mortality</title>
2141		---
2142		> <title>Parrot - Untitled</title>
2143		7c7
2144		< href="../../../resources/parrot.css"
2145		---
2146		> href="/parrot.css"
2147		17c17
2148		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2149		---
2150		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2151		23c23
2152		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Infant Mortality
2153		---
2154		> Untitled
	1960	< Copyright © 2002-2010, Parrot Foundation.
	1961	---
	1962	> Copyright © 2002-2009, Parrot Foundation.
	1963	diff -r parrot/docs/html/docs/dev/infant.pod.html parrot-trunk/docs/html/docs/dev/infant.pod.html
	1964	5c5
	1965	< <title>Parrot - Untitled</title>
	1966	---
	1967	> <title>Parrot - Infant Mortality</title>
	1968	23c23
	1969	< Untitled
	1970	---
	1971	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Infant Mortality
2155	1972	298c298
2156		< Copyright © 2002-2009, Parrot Foundation.
2157		---
2158		> Copyright © 2002-2010, Parrot Foundation.
2159		diff -r parrot-trunk/docs/html/docs/dev/longopt.pod.html parrot/docs/html/docs/dev/longopt.pod.html
2160		5c5
2161		< <title>Parrot - Long option parsing</title>
2162		---
2163		> <title>Parrot - Untitled</title>
2164		7c7
2165		< href="../../../resources/parrot.css"
2166		---
2167		> href="/parrot.css"
2168		17c17
2169		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2170		---
2171		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2172		23c23
2173		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Long option parsing
2174		---
2175		> Untitled
	1973	< Copyright © 2002-2010, Parrot Foundation.
	1974	---
	1975	> Copyright © 2002-2009, Parrot Foundation.
	1976	diff -r parrot/docs/html/docs/dev/longopt.pod.html parrot-trunk/docs/html/docs/dev/longopt.pod.html
	1977	5c5
	1978	< <title>Parrot - Untitled</title>
	1979	---
	1980	> <title>Parrot - Long option parsing</title>
	1981	23c23
	1982	< Untitled
	1983	---
	1984	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Long option parsing
2176	1985	98c98
2177		< Copyright © 2002-2009, Parrot Foundation.
2178		---
2179		> Copyright © 2002-2010, Parrot Foundation.
2180		diff -r parrot-trunk/docs/html/docs/dev/optimizer.pod.html parrot/docs/html/docs/dev/optimizer.pod.html
2181		5c5
2182		< <title>Parrot - About the IMCC optimizer</title>
2183		---
2184		> <title>Parrot - Untitled</title>
2185		7c7
2186		< href="../../../resources/parrot.css"
2187		---
2188		> href="/parrot.css"
2189		17c17
2190		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2191		---
2192		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2193		23c23
2194		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » About the IMCC optimizer
2195		---
2196		> Untitled
	1986	< Copyright © 2002-2010, Parrot Foundation.
	1987	---
	1988	> Copyright © 2002-2009, Parrot Foundation.
	1989	diff -r parrot/docs/html/docs/dev/optimizer.pod.html parrot-trunk/docs/html/docs/dev/optimizer.pod.html
	1990	5c5
	1991	< <title>Parrot - Untitled</title>
	1992	---
	1993	> <title>Parrot - About the IMCC optimizer</title>
	1994	23c23
	1995	< Untitled
	1996	---
	1997	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » About the IMCC optimizer
2197	1998	165c165
2198		< Copyright © 2002-2009, Parrot Foundation.
2199		---
2200		> Copyright © 2002-2010, Parrot Foundation.
2201		diff -r parrot-trunk/docs/html/docs/dev/parrot_api.pod.html parrot/docs/html/docs/dev/parrot_api.pod.html
2202		5c5
2203		< <title>Parrot - Notes on the PARROT_EXPORT macro</title>
2204		---
2205		> <title>Parrot - Untitled</title>
2206		7c7
2207		< href="../../../resources/parrot.css"
2208		---
2209		> href="/parrot.css"
2210		17c17
2211		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2212		---
2213		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2214		23c23
2215		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Notes on the PARROT_EXPORT macro
2216		---
2217		> Untitled
	1999	< Copyright © 2002-2010, Parrot Foundation.
	2000	---
	2001	> Copyright © 2002-2009, Parrot Foundation.
	2002	diff -r parrot/docs/html/docs/dev/parrot_api.pod.html parrot-trunk/docs/html/docs/dev/parrot_api.pod.html
	2003	5c5
	2004	< <title>Parrot - Untitled</title>
	2005	---
	2006	> <title>Parrot - Notes on the PARROT_EXPORT macro</title>
	2007	23c23
	2008	< Untitled
	2009	---
	2010	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Notes on the PARROT_EXPORT macro
2218	2011	64c64
2219		< Copyright © 2002-2009, Parrot Foundation.
2220		---
2221		> Copyright © 2002-2010, Parrot Foundation.
2222		diff -r parrot-trunk/docs/html/docs/dev/pccmethods.pod.html parrot/docs/html/docs/dev/pccmethods.pod.html
2223		5c5
2224		< <title>Parrot - Parrot Calling Conventions in C</title>
2225		---
2226		> <title>Parrot - Untitled</title>
2227		7c7
2228		< href="../../../resources/parrot.css"
2229		---
2230		> href="/parrot.css"
2231		17c17
2232		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2233		---
2234		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2235		23c23
2236		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Parrot Calling Conventions in C
2237		---
2238		> Untitled
	2012	< Copyright © 2002-2010, Parrot Foundation.
	2013	---
	2014	> Copyright © 2002-2009, Parrot Foundation.
	2015	diff -r parrot/docs/html/docs/dev/pccmethods.pod.html parrot-trunk/docs/html/docs/dev/pccmethods.pod.html
	2016	5c5
	2017	< <title>Parrot - Untitled</title>
	2018	---
	2019	> <title>Parrot - Parrot Calling Conventions in C</title>
	2020	23c23
	2021	< Untitled
	2022	---
	2023	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Parrot Calling Conventions in C
2239	2024	115c115
2240		< <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>
2241		---
2242		> <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>
	2025	< <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>
	2026	---
	2027	> <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>
2243	2028	141c141
2244		< Copyright © 2002-2009, Parrot Foundation.
2245		---
2246		> Copyright © 2002-2010, Parrot Foundation.
2247		diff -r parrot-trunk/docs/html/docs/dev/pcc_state.pod.html parrot/docs/html/docs/dev/pcc_state.pod.html
2248		5c5
2249		< <title>Parrot - parrot calling conventions state table</title>
2250		---
2251		> <title>Parrot - Untitled</title>
2252		7c7
2253		< href="../../../resources/parrot.css"
2254		---
2255		> href="/parrot.css"
2256		17c17
2257		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2258		---
2259		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2260		23c23
2261		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » parrot calling conventions state table
2262		---
2263		> Untitled
	2029	< Copyright © 2002-2010, Parrot Foundation.
	2030	---
	2031	> Copyright © 2002-2009, Parrot Foundation.
	2032	diff -r parrot/docs/html/docs/dev/pcc_state.pod.html parrot-trunk/docs/html/docs/dev/pcc_state.pod.html
	2033	5c5
	2034	< <title>Parrot - Untitled</title>
	2035	---
	2036	> <title>Parrot - parrot calling conventions state table</title>
	2037	23c23
	2038	< Untitled
	2039	---
	2040	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » parrot calling conventions state table
2264	2041	134c134
2265		< Copyright © 2002-2009, Parrot Foundation.
2266		---
2267		> Copyright © 2002-2010, Parrot Foundation.
2268		diff -r parrot-trunk/docs/html/docs/dev/pmc_freeze.pod.html parrot/docs/html/docs/dev/pmc_freeze.pod.html
2269		5c5
2270		< <title>Parrot - Freeze/Thaw Design Notes</title>
2271		---
2272		> <title>Parrot - Untitled</title>
2273		7c7
2274		< href="../../../resources/parrot.css"
2275		---
2276		> href="/parrot.css"
2277		17c17
2278		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2279		---
2280		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2281		23c23
2282		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Freeze/Thaw Design Notes
2283		---
2284		> Untitled
	2042	< Copyright © 2002-2010, Parrot Foundation.
	2043	---
	2044	> Copyright © 2002-2009, Parrot Foundation.
	2045	diff -r parrot/docs/html/docs/dev/pmc_freeze.pod.html parrot-trunk/docs/html/docs/dev/pmc_freeze.pod.html
	2046	5c5
	2047	< <title>Parrot - Untitled</title>
	2048	---
	2049	> <title>Parrot - Freeze/Thaw Design Notes</title>
	2050	23c23
	2051	< Untitled
	2052	---
	2053	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Freeze/Thaw Design Notes
2285	2054	215c215
2286		< <p><em>~~<a href="../../src/pmc_freeze.c.html">src/pmc_freeze.c</a>~~</em>, <em>pf/pf_items.c</em></p>
2287		---
2288		> <p><em>~~src/pmc_freeze.c~~</em>, <em>pf/pf_items.c</em></p>
	2055	< <p><em>src/pmc_freeze.c</em>, <em>pf/pf_items.c</em></p>
	2056	---
	2057	> <p><em><a href="../../src/pmc_freeze.c.html">src/pmc_freeze.c</a></em>, <em>pf/pf_items.c</em></p>
2289	2058	224c224
2290		< Copyright © 2002-2009, Parrot Foundation.
2291		---
2292		> Copyright © 2002-2010, Parrot Foundation.
2293		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
2294		5c5
2295		< <title>Parrot - Parrot PMC/Object Design Meeting Notes</title>
2296		---
2297		> <title>Parrot - Untitled</title>
2298		7c7
2299		< href="../../../resources/parrot.css"
2300		---
2301		> href="/parrot.css"
2302		17c17
2303		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2304		---
2305		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2306		23c23
2307		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Parrot PMC/Object Design Meeting Notes
2308		---
2309		> Untitled
	2059	< Copyright © 2002-2010, Parrot Foundation.
	2060	---
	2061	> Copyright © 2002-2009, Parrot Foundation.
	2062	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
	2063	5c5
	2064	< <title>Parrot - Untitled</title>
	2065	---
	2066	> <title>Parrot - Parrot PMC/Object Design Meeting Notes</title>
	2067	23c23
	2068	< Untitled
	2069	---
	2070	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Parrot PMC/Object Design Meeting Notes
2310	2071	190c190
2311		< Copyright © 2002-2009, Parrot Foundation.
2312		---
2313		> Copyright © 2002-2010, Parrot Foundation.
2314		diff -r parrot-trunk/docs/html/docs/dev/profiling.pod.html parrot/docs/html/docs/dev/profiling.pod.html
2315		5c5
2316		< <title>Parrot - Name</title>
2317		---
2318		> <title>Parrot - Untitled</title>
2319		7c7
2320		< href="../../../resources/parrot.css"
2321		---
2322		> href="/parrot.css"
2323		17c17
2324		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2325		---
2326		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2327		23c23
2328		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Name
2329		---
2330		> Untitled
	2072	< Copyright © 2002-2010, Parrot Foundation.
	2073	---
	2074	> Copyright © 2002-2009, Parrot Foundation.
	2075	diff -r parrot/docs/html/docs/dev/profiling.pod.html parrot-trunk/docs/html/docs/dev/profiling.pod.html
	2076	5c5
	2077	< <title>Parrot - Untitled</title>
	2078	---
	2079	> <title>Parrot - Name</title>
	2080	23c23
	2081	< Untitled
	2082	---
	2083	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/developer.html">Developer Documentation</a> » Name
2331	2084	91c91
2332		< Copyright © 2002-2009, Parrot Foundation.
2333		---
2334		> Copyright © 2002-2010, Parrot Foundation.
2335		diff -r parrot-trunk/docs/html/docs/embed.pod.html parrot/docs/html/docs/embed.pod.html
2336		5c5
2337		< <title>Parrot - Parrot embedding system</title>
2338		---
2339		> <title>Parrot - Untitled</title>
2340		7c7
2341		< href="../../resources/parrot.css"
2342		---
2343		> href="/parrot.css"
2344		17c17
2345		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2346		---
2347		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2348		23c23
2349		< <a href="../../html/index.html">Home</a> » <a href="../../html/developer.html">Developer Documentation</a> » Parrot embedding system
2350		---
2351		> Untitled
	2085	< Copyright © 2002-2010, Parrot Foundation.
	2086	---
	2087	> Copyright © 2002-2009, Parrot Foundation.
	2088	diff -r parrot/docs/html/docs/embed.pod.html parrot-trunk/docs/html/docs/embed.pod.html
	2089	5c5
	2090	< <title>Parrot - Untitled</title>
	2091	---
	2092	> <title>Parrot - Parrot embedding system</title>
	2093	23c23
	2094	< Untitled
	2095	---
	2096	> <a href="../../html/index.html">Home</a> » <a href="../../html/developer.html">Developer Documentation</a> » Parrot embedding system
2352	2097	2224c2224
2353		< <p><em>~~<a href="../src/main.c.html">src/main.c</a>~~</em> and <em>t/src/*.t</em> for Parrot's use of the embedding system.</p>
2354		---
2355		> <p><em>~~src/main.c~~</em> and <em>t/src/*.t</em> for Parrot's use of the embedding system.</p>
	2098	< <p><em>src/main.c</em> and <em>t/src/*.t</em> for Parrot's use of the embedding system.</p>
	2099	---
	2100	> <p><em><a href="../src/main.c.html">src/main.c</a></em> and <em>t/src/*.t</em> for Parrot's use of the embedding system.</p>
2356	2101	2230c2230
2357		< Copyright © 2002-2009, Parrot Foundation.
2358		---
2359		> Copyright © 2002-2010, Parrot Foundation.
2360		diff -r parrot-trunk/docs/html/docs/gettingstarted.pod.html parrot/docs/html/docs/gettingstarted.pod.html
2361		5c5
2362		< <title>Parrot - Parrot Developer FAQ</title>
2363		---
2364		> <title>Parrot - Untitled</title>
2365		7c7
2366		< href="../../resources/parrot.css"
2367		---
2368		> href="/parrot.css"
2369		17c17
2370		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2371		---
2372		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2373		23c23
2374		< <a href="../../html/index.html">Home</a> » Parrot Developer FAQ
2375		---
2376		> Untitled
	2102	< Copyright © 2002-2010, Parrot Foundation.
	2103	---
	2104	> Copyright © 2002-2009, Parrot Foundation.
	2105	diff -r parrot/docs/html/docs/gettingstarted.pod.html parrot-trunk/docs/html/docs/gettingstarted.pod.html
	2106	5c5
	2107	< <title>Parrot - Untitled</title>
	2108	---
	2109	> <title>Parrot - Parrot Developer FAQ</title>
	2110	23c23
	2111	< Untitled
	2112	---
	2113	> <a href="../../html/index.html">Home</a> » Parrot Developer FAQ
2377	2114	97c97
2378		< <p>There are a few categories of documentation, each with different intents. It'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's the executive summary:</p>
2379		---
2380		> <p>There are a few categories of documentation, each with different intents. It'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's the executive summary:</p>
	2115	< <p>There are a few categories of documentation, each with different intents. It'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's the executive summary:</p>
	2116	---
	2117	> <p>There are a few categories of documentation, each with different intents. It'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's the executive summary:</p>
2381	2118	170c170
2382		< <p>See <em>~~<a href="submissions.pod.html">docs/submissions.pod</a>~~</em> for details.</p>
2383		---
2384		> <p>See <em>~~docs/submissions.pod~~</em> for details.</p>
	2119	< <p>See <em>docs/submissions.pod</em> for details.</p>
	2120	---
	2121	> <p>See <em><a href="submissions.pod.html">docs/submissions.pod</a></em> for details.</p>
2385	2122	175c175
2386		< <p>See <em>~~<a href="submissions.pod.html">docs/submissions.pod</a>~~</em> for details.</p>
2387		---
2388		> <p>See <em>~~docs/submissions.pod~~</em> for details.</p>
	2123	< <p>See <em>docs/submissions.pod</em> for details.</p>
	2124	---
	2125	> <p>See <em><a href="submissions.pod.html">docs/submissions.pod</a></em> for details.</p>
2389	2126	184c184
2390		< Copyright © 2002-2009, Parrot Foundation.
2391		---
2392		> Copyright © 2002-2010, Parrot Foundation.
2393		diff -r parrot-trunk/docs/html/docs/glossary.pod.html parrot/docs/html/docs/glossary.pod.html
2394		5c5
2395		< <title>Parrot - Parrot Glossary</title>
2396		---
2397		> <title>Parrot - Untitled</title>
2398		7c7
2399		< href="../../resources/parrot.css"
2400		---
2401		> href="/parrot.css"
2402		17c17
2403		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2404		---
2405		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2406		23c23
2407		< <a href="../../html/index.html">Home</a> » Parrot Glossary
2408		---
2409		> Untitled
	2127	< Copyright © 2002-2010, Parrot Foundation.
	2128	---
	2129	> Copyright © 2002-2009, Parrot Foundation.
	2130	diff -r parrot/docs/html/docs/glossary.pod.html parrot-trunk/docs/html/docs/glossary.pod.html
	2131	5c5
	2132	< <title>Parrot - Untitled</title>
	2133	---
	2134	> <title>Parrot - Parrot Glossary</title>
	2135	23c23
	2136	< Untitled
	2137	---
	2138	> <a href="../../html/index.html">Home</a> » Parrot Glossary
2410	2139	206c206
2411		< Copyright © 2002-2009, Parrot Foundation.
2412		---
2413		> Copyright © 2002-2010, Parrot Foundation.
2414		diff -r parrot-trunk/docs/html/docs/intro.pod.html parrot/docs/html/docs/intro.pod.html
2415		5c5
2416		< <title>Parrot - The Parrot Primer</title>
2417		---
2418		> <title>Parrot - Untitled</title>
2419		7c7
2420		< href="../../resources/parrot.css"
2421		---
2422		> href="/parrot.css"
2423		17c17
2424		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2425		---
2426		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2427		23c23
2428		< <a href="../../html/index.html">Home</a> » The Parrot Primer
2429		---
2430		> Untitled
	2140	< Copyright © 2002-2010, Parrot Foundation.
	2141	---
	2142	> Copyright © 2002-2009, Parrot Foundation.
	2143	diff -r parrot/docs/html/docs/intro.pod.html parrot-trunk/docs/html/docs/intro.pod.html
	2144	5c5
	2145	< <title>Parrot - Untitled</title>
	2146	---
	2147	> <title>Parrot - The Parrot Primer</title>
	2148	23c23
	2149	< Untitled
	2150	---
	2151	> <a href="../../html/index.html">Home</a> » The Parrot Primer
2431	2152	181c181
2432		< <p>The first step to building Parrot is to run the <em>~~<a href="../Configure.pl.html">Configure.pl</a>~~</em> program,
2433		---
2434		> <p>The first step to building Parrot is to run the <em>~~Configure.pl~~</em> program,
	2153	< <p>The first step to building Parrot is to run the <em>Configure.pl</em> program,
	2154	---
	2155	> <p>The first step to building Parrot is to run the <em><a href="../Configure.pl.html">Configure.pl</a></em> program,
2435	2156	399c399
2436		< Copyright © 2002-2009, Parrot Foundation.
2437		---
2438		> Copyright © 2002-2010, Parrot Foundation.
2439		diff -r parrot-trunk/docs/html/docs/memory_internals.pod.html parrot/docs/html/docs/memory_internals.pod.html
2440		5c5
2441		< <title>Parrot - Memory Internals</title>
2442		---
2443		> <title>Parrot - Untitled</title>
2444		7c7
2445		< href="../../resources/parrot.css"
2446		---
2447		> href="/parrot.css"
2448		17c17
2449		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2450		---
2451		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2452		23c23
2453		< <a href="../../html/index.html">Home</a> » <a href="../../html/developer.html">Developer Documentation</a> » Memory Internals
2454		---
2455		> Untitled
	2157	< Copyright © 2002-2010, Parrot Foundation.
	2158	---
	2159	> Copyright © 2002-2009, Parrot Foundation.
	2160	diff -r parrot/docs/html/docs/memory_internals.pod.html parrot-trunk/docs/html/docs/memory_internals.pod.html
	2161	5c5
	2162	< <title>Parrot - Untitled</title>
	2163	---
	2164	> <title>Parrot - Memory Internals</title>
	2165	23c23
	2166	< Untitled
	2167	---
	2168	> <a href="../../html/index.html">Home</a> » <a href="../../html/developer.html">Developer Documentation</a> » Memory Internals
2456	2169	72c72
2457		< <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>
2458		---
2459		> <p>See <em>~~docs/pdds/pdd09_gc.pod~~</em> for details about the garbage collector system.</p>
	2170	< <p>See <em>docs/pdds/pdd09_gc.pod</em> for details about the garbage collector system.</p>
	2171	---
	2172	> <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>
2460	2173	160c160
2461		< <p>The <em>~~<a href="../Configure.pl.html">Configure.pl</a>~~</em> option <code>--gc</code> allows one to use either method.</p>
2462		---
2463		> <p>The <em>~~Configure.pl~~</em> option <code>--gc</code> allows one to use either method.</p>
	2174	< <p>The <em>Configure.pl</em> option <code>--gc</code> allows one to use either method.</p>
	2175	---
	2176	> <p>The <em><a href="../Configure.pl.html">Configure.pl</a></em> option <code>--gc</code> allows one to use either method.</p>
2464	2177	221c221
2465		< Copyright © 2002-2009, Parrot Foundation.
2466		---
2467		> Copyright © 2002-2010, Parrot Foundation.
	2178	< Copyright © 2002-2010, Parrot Foundation.
	2179	---
	2180	> Copyright © 2002-2009, Parrot Foundation.
2468	2181	Only in parrot-trunk/docs/html/docs: ops
2469		diff -r parrot-trunk/docs/html/docs/overview.pod.html parrot/docs/html/docs/overview.pod.html
2470		5c5
2471		< <title>Parrot - A Parrot Overview</title>
2472		---
2473		> <title>Parrot - Untitled</title>
2474		7c7
2475		< href="../../resources/parrot.css"
2476		---
2477		> href="/parrot.css"
2478		17c17
2479		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2480		---
2481		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2482		23c23
2483		< <a href="../../html/index.html">Home</a> » A Parrot Overview
2484		---
2485		> Untitled
	2182	diff -r parrot/docs/html/docs/overview.pod.html parrot-trunk/docs/html/docs/overview.pod.html
	2183	5c5
	2184	< <title>Parrot - Untitled</title>
	2185	---
	2186	> <title>Parrot - A Parrot Overview</title>
	2187	23c23
	2188	< Untitled
	2189	---
	2190	> <a href="../../html/index.html">Home</a> » A Parrot Overview
2486	2191	159c159
2487		< <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>
2488		---
2489		> <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>
	2192	< <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>
	2193	---
	2194	> <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>
2490	2195	181c181
2491		< <p>The bytecode format is fully documented in <em>~~<a href="parrotbyte.pod.html">docs/parrotbyte.pod</a>~~</em>.</p>
2492		---
2493		> <p>The bytecode format is fully documented in <em>~~docs/parrotbyte.pod~~</em>.</p>
	2196	< <p>The bytecode format is fully documented in <em>docs/parrotbyte.pod</em>.</p>
	2197	---
	2198	> <p>The bytecode format is fully documented in <em><a href="parrotbyte.pod.html">docs/parrotbyte.pod</a></em>.</p>
2494	2199	185c185
2495		< Copyright © 2002-2009, Parrot Foundation.
2496		---
2497		> Copyright © 2002-2010, Parrot Foundation.
	2200	< Copyright © 2002-2010, Parrot Foundation.
	2201	---
	2202	> Copyright © 2002-2009, Parrot Foundation.
2498	2203	Only in parrot-trunk/docs/html/docs: packfile-c.pod.html
2499		diff -r parrot-trunk/docs/html/docs/parrotbyte.pod.html parrot/docs/html/docs/parrotbyte.pod.html
2500		5c5
2501		< <title>Parrot - The Parrot Bytecode (PBC) Format</title>
2502		---
2503		> <title>Parrot - Untitled</title>
2504		7c7
2505		< href="../../resources/parrot.css"
2506		---
2507		> href="/parrot.css"
2508		17c17
2509		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2510		---
2511		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2512		23c23
2513		< <a href="../../html/index.html">Home</a> » <a href="../../html/developer.html">Developer Documentation</a> » The Parrot Bytecode (PBC) Format
2514		---
2515		> Untitled
	2204	diff -r parrot/docs/html/docs/parrotbyte.pod.html parrot-trunk/docs/html/docs/parrotbyte.pod.html
	2205	5c5
	2206	< <title>Parrot - Untitled</title>
	2207	---
	2208	> <title>Parrot - The Parrot Bytecode (PBC) Format</title>
	2209	23c23
	2210	< Untitled
	2211	---
	2212	> <a href="../../html/index.html">Home</a> » <a href="../../html/developer.html">Developer Documentation</a> » The Parrot Bytecode (PBC) Format
2516	2213	48c48
2517		< <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32-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>
2518		---
2519		> <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32-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>
	2214	< <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32-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>
	2215	---
	2216	> <p>The <b>Wordsize</b> (or <code>opcode_t</code> size) must be 4 (32-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>
2520	2217	319c319
2521		< Copyright © 2002-2009, Parrot Foundation.
2522		---
2523		> Copyright © 2002-2010, Parrot Foundation.
2524		diff -r parrot-trunk/docs/html/docs/parrothist.pod.html parrot/docs/html/docs/parrothist.pod.html
2525		5c5
2526		< <title>Parrot - Parrot Release History</title>
2527		---
2528		> <title>Parrot - Untitled</title>
2529		7c7
2530		< href="../../resources/parrot.css"
2531		---
2532		> href="/parrot.css"
2533		17c17
2534		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2535		---
2536		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2537		23c23
2538		< <a href="../../html/index.html">Home</a> » Parrot Release History
2539		---
2540		> Untitled
	2218	< Copyright © 2002-2010, Parrot Foundation.
	2219	---
	2220	> Copyright © 2002-2009, Parrot Foundation.
	2221	diff -r parrot/docs/html/docs/parrothist.pod.html parrot-trunk/docs/html/docs/parrothist.pod.html
	2222	5c5
	2223	< <title>Parrot - Untitled</title>
	2224	---
	2225	> <title>Parrot - Parrot Release History</title>
	2226	23c23
	2227	< Untitled
	2228	---
	2229	> <a href="../../html/index.html">Home</a> » Parrot Release History
2541	2230	158c158
2542		< Copyright © 2002-2009, Parrot Foundation.
2543		---
2544		> Copyright © 2002-2010, Parrot Foundation.
2545		diff -r parrot-trunk/docs/html/docs/parrot.pod.html parrot/docs/html/docs/parrot.pod.html
2546		5c5
2547		< <title>Parrot - Parrot</title>
2548		---
2549		> <title>Parrot - Untitled</title>
2550		7c7
2551		< href="../../resources/parrot.css"
2552		---
2553		> href="/parrot.css"
2554		17c17
2555		< <img border=0 src="../../resources/parrot_logo.png" id="logo" alt="parrot">
2556		---
2557		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2558		23c23
2559		< <a href="../../html/index.html">Home</a> » Parrot
2560		---
2561		> Untitled
	2231	< Copyright © 2002-2010, Parrot Foundation.
	2232	---
	2233	> Copyright © 2002-2009, Parrot Foundation.
	2234	diff -r parrot/docs/html/docs/parrot.pod.html parrot-trunk/docs/html/docs/parrot.pod.html
	2235	5c5
	2236	< <title>Parrot - Untitled</title>
	2237	---
	2238	> <title>Parrot - Parrot</title>
	2239	23c23
	2240	< Untitled
	2241	---
	2242	> <a href="../../html/index.html">Home</a> » Parrot
2562	2243	128c128
2563		< The list is archived at: <a href='http://groups.google.com/group/parrot-dev/'><a href="http://groups.google.com/group/parrot-dev/">http://groups.google.com/group/parrot-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>
2564		---
2565		> The list is archived at: <a href='http://groups.google.com/group/parrot-dev/'><a href="http://groups.google.com/group/parrot-dev/">http://groups.google.com/group/parrot-dev/</a></a> Many people have contributed their time and expertise to the Parrot project; see the <em>~~CREDITS~~</em> file for details.</p>
	2244	< The list is archived at: <a href='http://groups.google.com/group/parrot-dev/'><a href="http://groups.google.com/group/parrot-dev/">http://groups.google.com/group/parrot-dev/</a></a> Many people have contributed their time and expertise to the Parrot project; see the <em>CREDITS</em> file for details.</p>
	2245	---
	2246	> The list is archived at: <a href='http://groups.google.com/group/parrot-dev/'><a href="http://groups.google.com/group/parrot-dev/">http://groups.google.com/group/parrot-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>
2566	2247	147c147
2567		< Copyright © 2002-2009, Parrot Foundation.
2568		---
2569		> Copyright © 2002-2010, Parrot Foundation.
	2248	< Copyright © 2002-2010, Parrot Foundation.
	2249	---
	2250	> Copyright © 2002-2009, Parrot Foundation.
2570	2251	Only in parrot-trunk/docs/html/docs: pct
2571		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd01_overview.pod.html parrot/docs/html/docs/pdds/draft/pdd01_overview.pod.html
2572		5c5
2573		< <title>Parrot - [DRAFT] PDD 1: Overview</title>
2574		---
2575		> <title>Parrot - Untitled</title>
2576		7c7
2577		< href="../../../../resources/parrot.css"
2578		---
2579		> href="/parrot.css"
2580		17c17
2581		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2582		---
2583		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2584		23c23
2585		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 1: Overview
2586		---
2587		> Untitled
	2252	diff -r parrot/docs/html/docs/pdds/draft/pdd01_overview.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd01_overview.pod.html
	2253	5c5
	2254	< <title>Parrot - Untitled</title>
	2255	---
	2256	> <title>Parrot - [DRAFT] PDD 1: Overview</title>
	2257	23c23
	2258	< Untitled
	2259	---
	2260	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 1: Overview
2588	2261	306c306
2589		< Copyright © 2002-2009, Parrot Foundation.
2590		---
2591		> Copyright © 2002-2010, Parrot Foundation.
2592		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html parrot/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html
2593		5c5
2594		< <title>Parrot - [DRAFT] PDD 5: Opcodes</title>
2595		---
2596		> <title>Parrot - Untitled</title>
2597		7c7
2598		< href="../../../../resources/parrot.css"
2599		---
2600		> href="/parrot.css"
2601		17c17
2602		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2603		---
2604		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2605		23c23
2606		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 5: Opcodes
2607		---
2608		> Untitled
	2262	< Copyright © 2002-2010, Parrot Foundation.
	2263	---
	2264	> Copyright © 2002-2009, Parrot Foundation.
	2265	diff -r parrot/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd05_opfunc.pod.html
	2266	5c5
	2267	< <title>Parrot - Untitled</title>
	2268	---
	2269	> <title>Parrot - [DRAFT] PDD 5: Opcodes</title>
	2270	23c23
	2271	< Untitled
	2272	---
	2273	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 5: Opcodes
2609	2274	189c189
2610		< Copyright © 2002-2009, Parrot Foundation.
2611		---
2612		> Copyright © 2002-2010, Parrot Foundation.
2613		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd06_pasm.pod.html parrot/docs/html/docs/pdds/draft/pdd06_pasm.pod.html
2614		5c5
2615		< <title>Parrot - [DRAFT] PDD 6: Parrot Assembly Language (PASM)</title>
2616		---
2617		> <title>Parrot - Untitled</title>
2618		7c7
2619		< href="../../../../resources/parrot.css"
2620		---
2621		> href="/parrot.css"
2622		17c17
2623		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2624		---
2625		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2626		23c23
2627		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 6: Parrot Assembly Language (PASM)
2628		---
2629		> Untitled
	2275	< Copyright © 2002-2010, Parrot Foundation.
	2276	---
	2277	> Copyright © 2002-2009, Parrot Foundation.
	2278	diff -r parrot/docs/html/docs/pdds/draft/pdd06_pasm.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd06_pasm.pod.html
	2279	5c5
	2280	< <title>Parrot - Untitled</title>
	2281	---
	2282	> <title>Parrot - [DRAFT] PDD 6: Parrot Assembly Language (PASM)</title>
	2283	23c23
	2284	< Untitled
	2285	---
	2286	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 6: Parrot Assembly Language (PASM)
2630	2287	168c168
2631		< Copyright © 2002-2009, Parrot Foundation.
2632		---
2633		> Copyright © 2002-2010, Parrot Foundation.
2634		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd08_keys.pod.html parrot/docs/html/docs/pdds/draft/pdd08_keys.pod.html
2635		5c5
2636		< <title>Parrot - [DRAFT] PDD 8: PMC Keys</title>
2637		---
2638		> <title>Parrot - Untitled</title>
2639		7c7
2640		< href="../../../../resources/parrot.css"
2641		---
2642		> href="/parrot.css"
2643		17c17
2644		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2645		---
2646		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2647		23c23
2648		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 8: PMC Keys
2649		---
2650		> Untitled
	2288	< Copyright © 2002-2010, Parrot Foundation.
	2289	---
	2290	> Copyright © 2002-2009, Parrot Foundation.
	2291	diff -r parrot/docs/html/docs/pdds/draft/pdd08_keys.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd08_keys.pod.html
	2292	5c5
	2293	< <title>Parrot - Untitled</title>
	2294	---
	2295	> <title>Parrot - [DRAFT] PDD 8: PMC Keys</title>
	2296	23c23
	2297	< Untitled
	2298	---
	2299	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 8: PMC Keys
2651	2300	214c214
2652		< Copyright © 2002-2009, Parrot Foundation.
2653		---
2654		> Copyright © 2002-2010, Parrot Foundation.
2655		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd10_embedding.pod.html parrot/docs/html/docs/pdds/draft/pdd10_embedding.pod.html
2656		5c5
2657		< <title>Parrot - [DRAFT] PDD10: Embedding and Extending</title>
2658		---
2659		> <title>Parrot - Untitled</title>
2660		7c7
2661		< href="../../../../resources/parrot.css"
2662		---
2663		> href="/parrot.css"
2664		17c17
2665		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2666		---
2667		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2668		23c23
2669		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD10: Embedding and Extending
2670		---
2671		> Untitled
	2301	< Copyright © 2002-2010, Parrot Foundation.
	2302	---
	2303	> Copyright © 2002-2009, Parrot Foundation.
	2304	diff -r parrot/docs/html/docs/pdds/draft/pdd10_embedding.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd10_embedding.pod.html
	2305	5c5
	2306	< <title>Parrot - Untitled</title>
	2307	---
	2308	> <title>Parrot - [DRAFT] PDD10: Embedding and Extending</title>
	2309	23c23
	2310	< Untitled
	2311	---
	2312	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD10: Embedding and Extending
2672	2313	260c260
2673		< Copyright © 2002-2009, Parrot Foundation.
2674		---
2675		> Copyright © 2002-2010, Parrot Foundation.
2676		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd11_extending.pod.html parrot/docs/html/docs/pdds/draft/pdd11_extending.pod.html
2677		5c5
2678		< <title>Parrot - [DRAFT] PDD 11: Extending</title>
2679		---
2680		> <title>Parrot - Untitled</title>
2681		7c7
2682		< href="../../../../resources/parrot.css"
2683		---
2684		> href="/parrot.css"
2685		17c17
2686		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2687		---
2688		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2689		23c23
2690		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 11: Extending
2691		---
2692		> Untitled
	2314	< Copyright © 2002-2010, Parrot Foundation.
	2315	---
	2316	> Copyright © 2002-2009, Parrot Foundation.
	2317	diff -r parrot/docs/html/docs/pdds/draft/pdd11_extending.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd11_extending.pod.html
	2318	5c5
	2319	< <title>Parrot - Untitled</title>
	2320	---
	2321	> <title>Parrot - [DRAFT] PDD 11: Extending</title>
	2322	23c23
	2323	< Untitled
	2324	---
	2325	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 11: Extending
2693	2326	40c40
2694		< <p>$Revision: 4~~7669~~ $</p>
2695		---
2696		> <p>$Revision: 4~~8025~~ $</p>
	2327	< <p>$Revision: 48025 $</p>
	2328	---
	2329	> <p>$Revision: 47669 $</p>
2697	2330	326c326
2698		< <p><em>~~<a href="../../glossary.pod.html">docs/glossary.pod</a>~~</em></p>
2699		---
2700		> <p><em>~~docs/glossary.pod~~</em></p>
	2331	< <p><em>docs/glossary.pod</em></p>
	2332	---
	2333	> <p><em><a href="../../glossary.pod.html">docs/glossary.pod</a></em></p>
2701	2334	330c330
2702		< Copyright © 2002-2009, Parrot Foundation.
2703		---
2704		> Copyright © 2002-2010, Parrot Foundation.
2705		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd14_numbers.pod.html parrot/docs/html/docs/pdds/draft/pdd14_numbers.pod.html
2706		5c5
2707		< <title>Parrot - [DRAFT] PDD 14: Numbers</title>
2708		---
2709		> <title>Parrot - Untitled</title>
2710		7c7
2711		< href="../../../../resources/parrot.css"
2712		---
2713		> href="/parrot.css"
2714		17c17
2715		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2716		---
2717		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2718		23c23
2719		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 14: Numbers
2720		---
2721		> Untitled
	2335	< Copyright © 2002-2010, Parrot Foundation.
	2336	---
	2337	> Copyright © 2002-2009, Parrot Foundation.
	2338	diff -r parrot/docs/html/docs/pdds/draft/pdd14_numbers.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd14_numbers.pod.html
	2339	5c5
	2340	< <title>Parrot - Untitled</title>
	2341	---
	2342	> <title>Parrot - [DRAFT] PDD 14: Numbers</title>
	2343	23c23
	2344	< Untitled
	2345	---
	2346	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 14: Numbers
2722	2347	489c489
2723		< Copyright © 2002-2009, Parrot Foundation.
2724		---
2725		> Copyright © 2002-2010, Parrot Foundation.
2726		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
2727		5c5
2728		< <title>Parrot - [DRAFT] PDD 16: Native Call Interface (NCI)</title>
2729		---
2730		> <title>Parrot - Untitled</title>
2731		7c7
2732		< href="../../../../resources/parrot.css"
2733		---
2734		> href="/parrot.css"
2735		17c17
2736		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2737		---
2738		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2739		23c23
2740		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 16: Native Call Interface (NCI)
2741		---
2742		> Untitled
	2348	< Copyright © 2002-2010, Parrot Foundation.
	2349	---
	2350	> Copyright © 2002-2009, Parrot Foundation.
	2351	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
	2352	5c5
	2353	< <title>Parrot - Untitled</title>
	2354	---
	2355	> <title>Parrot - [DRAFT] PDD 16: Native Call Interface (NCI)</title>
	2356	23c23
	2357	< Untitled
	2358	---
	2359	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 16: Native Call Interface (NCI)
2743	2360	319c319
2744		< <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>
2745		---
2746		> <p><em>~~t/pmc/nci.t</em>, <em>src/nci_test.c~~</em></p>
	2361	< <p><em>t/pmc/nci.t</em>, <em>src/nci_test.c</em></p>
	2362	---
	2363	> <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>
2747	2364	323c323
2748		< Copyright © 2002-2009, Parrot Foundation.
2749		---
2750		> Copyright © 2002-2010, Parrot Foundation.
2751		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
2752		5c5
2753		< <title>Parrot - [DRAFT] PDD 29: Compiler Tools</title>
2754		---
2755		> <title>Parrot - Untitled</title>
2756		7c7
2757		< href="../../../../resources/parrot.css"
2758		---
2759		> href="/parrot.css"
2760		17c17
2761		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2762		---
2763		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2764		23c23
2765		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 29: Compiler Tools
2766		---
2767		> Untitled
	2365	< Copyright © 2002-2010, Parrot Foundation.
	2366	---
	2367	> Copyright © 2002-2009, Parrot Foundation.
	2368	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
	2369	5c5
	2370	< <title>Parrot - Untitled</title>
	2371	---
	2372	> <title>Parrot - [DRAFT] PDD 29: Compiler Tools</title>
	2373	23c23
	2374	< Untitled
	2375	---
	2376	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 29: Compiler Tools
2768	2377	339c339
2769		< Copyright © 2002-2009, Parrot Foundation.
2770		---
2771		> Copyright © 2002-2010, Parrot Foundation.
2772		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
2773		5c5
2774		< <title>Parrot - [DRAFT] PDD 31: Inter-Language Calling</title>
2775		---
2776		> <title>Parrot - Untitled</title>
2777		7c7
2778		< href="../../../../resources/parrot.css"
2779		---
2780		> href="/parrot.css"
2781		17c17
2782		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2783		---
2784		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2785		23c23
2786		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 31: Inter-Language Calling
2787		---
2788		> Untitled
	2378	< Copyright © 2002-2010, Parrot Foundation.
	2379	---
	2380	> Copyright © 2002-2009, Parrot Foundation.
	2381	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
	2382	5c5
	2383	< <title>Parrot - Untitled</title>
	2384	---
	2385	> <title>Parrot - [DRAFT] PDD 31: Inter-Language Calling</title>
	2386	23c23
	2387	< Untitled
	2388	---
	2389	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 31: Inter-Language Calling
2789	2390	373c373
2790		< Copyright © 2002-2009, Parrot Foundation.
2791		---
2792		> Copyright © 2002-2010, Parrot Foundation.
2793		diff -r parrot-trunk/docs/html/docs/pdds/draft/pdd31_hll.pod.html parrot/docs/html/docs/pdds/draft/pdd31_hll.pod.html
2794		5c5
2795		< <title>Parrot - [DRAFT] PDD 31: HLL Compilers and Libraries</title>
2796		---
2797		> <title>Parrot - Untitled</title>
2798		7c7
2799		< href="../../../../resources/parrot.css"
2800		---
2801		> href="/parrot.css"
2802		17c17
2803		< <img border=0 src="../../../../resources/parrot_logo.png" id="logo" alt="parrot">
2804		---
2805		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2806		23c23
2807		< <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 31: HLL Compilers and Libraries
2808		---
2809		> Untitled
	2391	< Copyright © 2002-2010, Parrot Foundation.
	2392	---
	2393	> Copyright © 2002-2009, Parrot Foundation.
	2394	diff -r parrot/docs/html/docs/pdds/draft/pdd31_hll.pod.html parrot-trunk/docs/html/docs/pdds/draft/pdd31_hll.pod.html
	2395	5c5
	2396	< <title>Parrot - Untitled</title>
	2397	---
	2398	> <title>Parrot - [DRAFT] PDD 31: HLL Compilers and Libraries</title>
	2399	23c23
	2400	< Untitled
	2401	---
	2402	> <a href="../../../../html/index.html">Home</a> » <a href="../../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » [DRAFT] PDD 31: HLL Compilers and Libraries
2810	2403	192c192
2811		< Copyright © 2002-2009, Parrot Foundation.
2812		---
2813		> Copyright © 2002-2010, Parrot Foundation.
2814		diff -r parrot-trunk/docs/html/docs/pdds/pdd00_pdd.pod.html parrot/docs/html/docs/pdds/pdd00_pdd.pod.html
2815		5c5
2816		< <title>Parrot - PDD 0: Design Document Format</title>
2817		---
2818		> <title>Parrot - Untitled</title>
2819		7c7
2820		< href="../../../resources/parrot.css"
2821		---
2822		> href="/parrot.css"
2823		17c17
2824		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2825		---
2826		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2827		23c23
2828		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 0: Design Document Format
2829		---
2830		> Untitled
	2404	< Copyright © 2002-2010, Parrot Foundation.
	2405	---
	2406	> Copyright © 2002-2009, Parrot Foundation.
	2407	diff -r parrot/docs/html/docs/pdds/pdd00_pdd.pod.html parrot-trunk/docs/html/docs/pdds/pdd00_pdd.pod.html
	2408	5c5
	2409	< <title>Parrot - Untitled</title>
	2410	---
	2411	> <title>Parrot - PDD 0: Design Document Format</title>
	2412	23c23
	2413	< Untitled
	2414	---
	2415	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 0: Design Document Format
2831	2416	92c92
2832		< An example of the currently accepted layout is given in <em>~~<a href="pdd_template.pod.html">docs/pdds/pdd_template.pod</a>~~</em>,
2833		---
2834		> An example of the currently accepted layout is given in <em>~~docs/pdds/pdd_template.pod~~</em>,
	2417	< An example of the currently accepted layout is given in <em>docs/pdds/pdd_template.pod</em>,
	2418	---
	2419	> An example of the currently accepted layout is given in <em><a href="pdd_template.pod.html">docs/pdds/pdd_template.pod</a></em>,
2835	2420	177c177
2836		< Copyright © 2002-2009, Parrot Foundation.
2837		---
2838		> Copyright © 2002-2010, Parrot Foundation.
2839		diff -r parrot-trunk/docs/html/docs/pdds/pdd03_calling_conventions.pod.html parrot/docs/html/docs/pdds/pdd03_calling_conventions.pod.html
2840		5c5
2841		< <title>Parrot - PDD 3: Calling Conventions</title>
2842		---
2843		> <title>Parrot - Untitled</title>
2844		7c7
2845		< href="../../../resources/parrot.css"
2846		---
2847		> href="/parrot.css"
2848		17c17
2849		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2850		---
2851		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2852		23c23
2853		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 3: Calling Conventions
2854		---
2855		> Untitled
	2421	< Copyright © 2002-2010, Parrot Foundation.
	2422	---
	2423	> Copyright © 2002-2009, Parrot Foundation.
	2424	diff -r parrot/docs/html/docs/pdds/pdd03_calling_conventions.pod.html parrot-trunk/docs/html/docs/pdds/pdd03_calling_conventions.pod.html
	2425	5c5
	2426	< <title>Parrot - Untitled</title>
	2427	---
	2428	> <title>Parrot - PDD 3: Calling Conventions</title>
	2429	23c23
	2430	< Untitled
	2431	---
	2432	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 3: Calling Conventions
2856	2433	299c299
2857		< Copyright © 2002-2009, Parrot Foundation.
2858		---
2859		> Copyright © 2002-2010, Parrot Foundation.
2860		diff -r parrot-trunk/docs/html/docs/pdds/pdd07_codingstd.pod.html parrot/docs/html/docs/pdds/pdd07_codingstd.pod.html
2861		5c5
2862		< <title>Parrot - PDD 7: Conventions and Guidelines for Parrot Source Code</title>
2863		---
2864		> <title>Parrot - Untitled</title>
2865		7c7
2866		< href="../../../resources/parrot.css"
2867		---
2868		> href="/parrot.css"
2869		17c17
2870		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2871		---
2872		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2873		23c23
2874		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 7: Conventions and Guidelines for Parrot Source Code
2875		---
2876		> Untitled
	2434	< Copyright © 2002-2010, Parrot Foundation.
	2435	---
	2436	> Copyright © 2002-2009, Parrot Foundation.
	2437	diff -r parrot/docs/html/docs/pdds/pdd07_codingstd.pod.html parrot-trunk/docs/html/docs/pdds/pdd07_codingstd.pod.html
	2438	5c5
	2439	< <title>Parrot - Untitled</title>
	2440	---
	2441	> <title>Parrot - PDD 7: Conventions and Guidelines for Parrot Source Code</title>
	2442	23c23
	2443	< Untitled
	2444	---
	2445	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 7: Conventions and Guidelines for Parrot Source Code
2877	2446	32c32
2878		< <p>$Revision: 4~~5652~~ $</p>
2879		---
2880		> <p>$Revision: 4~~7658~~ $</p>
	2447	< <p>$Revision: 47658 $</p>
	2448	---
	2449	> <p>$Revision: 45652 $</p>
2881	2450	410c410
2882		< <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>
2883		---
2884		> <p>The <em>~~t/distro/file_metadata.t~~</em> test checks that the files needing this property have it set.</p>
	2451	< <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
	2452	---
	2453	> <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>
2885	2454	423c423
2886		< <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>
2887		---
2888		> <p>The <em>~~t/distro/file_metadata.t~~</em> test checks that the files needing this property have it set.</p>
	2455	< <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
	2456	---
	2457	> <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>
2889	2458	428c428
2890		< <p>The <code>svn:eol-style</code> property makes sure that whenever a file is checked out of subversion it has the correct end-of-line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol-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-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>
2891		---
2892		> <p>The <code>svn:eol-style</code> property makes sure that whenever a file is checked out of subversion it has the correct end-of-line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol-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-style</code> property. The current list of such files is described in <em>~~t/distro/file_metadata.t~~</em>.</p>
	2459	< <p>The <code>svn:eol-style</code> property makes sure that whenever a file is checked out of subversion it has the correct end-of-line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol-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-style</code> property. The current list of such files is described in <em>t/distro/file_metadata.t</em>.</p>
	2460	---
	2461	> <p>The <code>svn:eol-style</code> property makes sure that whenever a file is checked out of subversion it has the correct end-of-line characters appropriate for the given platform. Therefore, most files should have their <code>svn:eol-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-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>
2893	2462	438c438
2894		< <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>
2895		---
2896		> <p>The <em>~~t/distro/file_metadata.t~~</em> test checks that the files needing this property have it set.</p>
	2463	< <p>The <em>t/distro/file_metadata.t</em> test checks that the files needing this property have it set.</p>
	2464	---
	2465	> <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>
2897	2466	567,569c567,569
2898		< This inline Pod documentation is ~~parsed to HTML by running~~:
2899		< <pre> $ ~~perl tools/docs/write_docs.pl --delete~~</pre>
2900		< ~~or: $ make html~~
2901		---
2902		> This inline Pod documentation is ~~transformed to HTML with~~:
2903		> <pre> $ ~~make html~~</pre>
2904		>
	2467	< This inline Pod documentation is transformed to HTML with:
	2468	< <pre> $ make html</pre>
	2469	<
	2470	---
	2471	> This inline Pod documentation is parsed to HTML by running:
	2472	> <pre> $ perl tools/docs/write_docs.pl --delete</pre>
	2473	> or: $ make html
2905	2474	640c640
2906		< Copyright © 2002-2009, Parrot Foundation.
2907		---
2908		> Copyright © 2002-2010, Parrot Foundation.
2909		diff -r parrot-trunk/docs/html/docs/pdds/pdd09_gc.pod.html parrot/docs/html/docs/pdds/pdd09_gc.pod.html
2910		5c5
2911		< <title>Parrot - PDD 9: Garbage Collection Subsystem</title>
2912		---
2913		> <title>Parrot - Untitled</title>
2914		7c7
2915		< href="../../../resources/parrot.css"
2916		---
2917		> href="/parrot.css"
2918		17c17
2919		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2920		---
2921		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2922		23c23
2923		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 9: Garbage Collection Subsystem
2924		---
2925		> Untitled
	2475	< Copyright © 2002-2010, Parrot Foundation.
	2476	---
	2477	> Copyright © 2002-2009, Parrot Foundation.
	2478	diff -r parrot/docs/html/docs/pdds/pdd09_gc.pod.html parrot-trunk/docs/html/docs/pdds/pdd09_gc.pod.html
	2479	5c5
	2480	< <title>Parrot - Untitled</title>
	2481	---
	2482	> <title>Parrot - PDD 9: Garbage Collection Subsystem</title>
	2483	23c23
	2484	< Untitled
	2485	---
	2486	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 9: Garbage Collection Subsystem
2926	2487	680c680
2927		< Copyright © 2002-2009, Parrot Foundation.
2928		---
2929		> Copyright © 2002-2010, Parrot Foundation.
2930		diff -r parrot-trunk/docs/html/docs/pdds/pdd13_bytecode.pod.html parrot/docs/html/docs/pdds/pdd13_bytecode.pod.html
2931		5c5
2932		< <title>Parrot - PDD 13: Bytecode</title>
2933		---
2934		> <title>Parrot - Untitled</title>
2935		7c7
2936		< href="../../../resources/parrot.css"
2937		---
2938		> href="/parrot.css"
2939		17c17
2940		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2941		---
2942		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2943		23c23
2944		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 13: Bytecode
2945		---
2946		> Untitled
	2488	< Copyright © 2002-2010, Parrot Foundation.
	2489	---
	2490	> Copyright © 2002-2009, Parrot Foundation.
	2491	diff -r parrot/docs/html/docs/pdds/pdd13_bytecode.pod.html parrot-trunk/docs/html/docs/pdds/pdd13_bytecode.pod.html
	2492	5c5
	2493	< <title>Parrot - Untitled</title>
	2494	---
	2495	> <title>Parrot - PDD 13: Bytecode</title>
	2496	23c23
	2497	< Untitled
	2498	---
	2499	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 13: Bytecode
2947	2500	990c990
2948		< Copyright © 2002-2009, Parrot Foundation.
2949		---
2950		> Copyright © 2002-2010, Parrot Foundation.
2951		diff -r parrot-trunk/docs/html/docs/pdds/pdd15_objects.pod.html parrot/docs/html/docs/pdds/pdd15_objects.pod.html
2952		5c5
2953		< <title>Parrot - PDD 15: Objects and Classes</title>
2954		---
2955		> <title>Parrot - Untitled</title>
2956		7c7
2957		< href="../../../resources/parrot.css"
2958		---
2959		> href="/parrot.css"
2960		17c17
2961		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2962		---
2963		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2964		23c23
2965		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 15: Objects and Classes
2966		---
2967		> Untitled
	2501	< Copyright © 2002-2010, Parrot Foundation.
	2502	---
	2503	> Copyright © 2002-2009, Parrot Foundation.
	2504	diff -r parrot/docs/html/docs/pdds/pdd15_objects.pod.html parrot-trunk/docs/html/docs/pdds/pdd15_objects.pod.html
	2505	5c5
	2506	< <title>Parrot - Untitled</title>
	2507	---
	2508	> <title>Parrot - PDD 15: Objects and Classes</title>
	2509	23c23
	2510	< Untitled
	2511	---
	2512	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 15: Objects and Classes
2968	2513	1273c1273
2969		< Copyright © 2002-2009, Parrot Foundation.
2970		---
2971		> Copyright © 2002-2010, Parrot Foundation.
2972		diff -r parrot-trunk/docs/html/docs/pdds/pdd17_pmc.pod.html parrot/docs/html/docs/pdds/pdd17_pmc.pod.html
2973		5c5
2974		< <title>Parrot - PDD 17: Polymorphic Containers</title>
2975		---
2976		> <title>Parrot - Untitled</title>
2977		7c7
2978		< href="../../../resources/parrot.css"
2979		---
2980		> href="/parrot.css"
2981		17c17
2982		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
2983		---
2984		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
2985		23c23
2986		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 17: Polymorphic Containers
2987		---
2988		> Untitled
	2514	< Copyright © 2002-2010, Parrot Foundation.
	2515	---
	2516	> Copyright © 2002-2009, Parrot Foundation.
	2517	diff -r parrot/docs/html/docs/pdds/pdd17_pmc.pod.html parrot-trunk/docs/html/docs/pdds/pdd17_pmc.pod.html
	2518	5c5
	2519	< <title>Parrot - Untitled</title>
	2520	---
	2521	> <title>Parrot - PDD 17: Polymorphic Containers</title>
	2522	23c23
	2523	< Untitled
	2524	---
	2525	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 17: Polymorphic Containers
2989	2526	91c91
2990		< <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>
2991		---
2992		> <p><code>_metadata</code> holds internal PMC metadata (properties). See the setprop/getprop ops in <em>~~docs/ops/pmc.pod~~</em>.</p>
	2527	< <p><code>_metadata</code> holds internal PMC metadata (properties). See the setprop/getprop ops in <em>docs/ops/pmc.pod</em>.</p>
	2528	---
	2529	> <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>
2993	2530	797c797
2994		< Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating-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's "corrected mod" algorithm, as implemented in <em>~~<a href="../../src/utils.c.html">src/utils.c</a>~~</em>, while <code>cmodulus</code> uses the C-style fmod function.
2995		---
2996		> Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating-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's "corrected mod" algorithm, as implemented in <em>~~src/utils.c~~</em>, while <code>cmodulus</code> uses the C-style fmod function.
	2531	< Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating-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's "corrected mod" algorithm, as implemented in <em>src/utils.c</em>, while <code>cmodulus</code> uses the C-style fmod function.
	2532	---
	2533	> Divide the value of the <i>self</i> PMC by the value of a PMC, native integer, or native floating-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's "corrected mod" algorithm, as implemented in <em><a href="../../src/utils.c.html">src/utils.c</a></em>, while <code>cmodulus</code> uses the C-style fmod function.
2997	2534	1228c1228
2998		< <p><em>~~<a href="../pmc2c.pod.html">docs/pmc2c.pod</a>~~</em></p>
2999		---
3000		> <p><em>~~docs/pmc2c.pod~~</em></p>
	2535	< <p><em>docs/pmc2c.pod</em></p>
	2536	---
	2537	> <p><em><a href="../pmc2c.pod.html">docs/pmc2c.pod</a></em></p>
3001	2538	1232c1232
3002		< Copyright © 2002-2009, Parrot Foundation.
3003		---
3004		> Copyright © 2002-2010, Parrot Foundation.
3005		diff -r parrot-trunk/docs/html/docs/pdds/pdd18_security.pod.html parrot/docs/html/docs/pdds/pdd18_security.pod.html
3006		5c5
3007		< <title>Parrot - PDD 18: Security Model</title>
3008		---
3009		> <title>Parrot - Untitled</title>
3010		7c7
3011		< href="../../../resources/parrot.css"
3012		---
3013		> href="/parrot.css"
3014		17c17
3015		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
3016		---
3017		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
3018		23c23
3019		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 18: Security Model
3020		---
3021		> Untitled
	2539	< Copyright © 2002-2010, Parrot Foundation.
	2540	---
	2541	> Copyright © 2002-2009, Parrot Foundation.
	2542	diff -r parrot/docs/html/docs/pdds/pdd18_security.pod.html parrot-trunk/docs/html/docs/pdds/pdd18_security.pod.html
	2543	5c5
	2544	< <title>Parrot - Untitled</title>
	2545	---
	2546	> <title>Parrot - PDD 18: Security Model</title>
	2547	23c23
	2548	< Untitled
	2549	---
	2550	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 18: Security Model
3022	2551	234c234
3023		< Copyright © 2002-2009, Parrot Foundation.
3024		---
3025		> Copyright © 2002-2010, Parrot Foundation.
3026		diff -r parrot-trunk/docs/html/docs/pdds/pdd19_pir.pod.html parrot/docs/html/docs/pdds/pdd19_pir.pod.html
3027		5c5
3028		< <title>Parrot - PDD 19: Parrot Intermediate Representation (PIR)</title>
3029		---
3030		> <title>Parrot - Untitled</title>
3031		7c7
3032		< href="../../../resources/parrot.css"
3033		---
3034		> href="/parrot.css"
3035		17c17
3036		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
3037		---
3038		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
3039		23c23
3040		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 19: Parrot Intermediate Representation (PIR)
3041		---
3042		> Untitled
	2552	< Copyright © 2002-2010, Parrot Foundation.
	2553	---
	2554	> Copyright © 2002-2009, Parrot Foundation.
	2555	diff -r parrot/docs/html/docs/pdds/pdd19_pir.pod.html parrot-trunk/docs/html/docs/pdds/pdd19_pir.pod.html
	2556	5c5
	2557	< <title>Parrot - Untitled</title>
	2558	---
	2559	> <title>Parrot - PDD 19: Parrot Intermediate Representation (PIR)</title>
	2560	23c23
	2561	< Untitled
	2562	---
	2563	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 19: Parrot Intermediate Representation (PIR)
3043	2564	838c838
3044		< Copyright © 2002-2009, Parrot Foundation.
3045		---
3046		> Copyright © 2002-2010, Parrot Foundation.
3047		diff -r parrot-trunk/docs/html/docs/pdds/pdd20_lexical_vars.pod.html parrot/docs/html/docs/pdds/pdd20_lexical_vars.pod.html
3048		5c5
3049		< <title>Parrot - PDD 20: Lexical Variables</title>
3050		---
3051		> <title>Parrot - Untitled</title>
3052		7c7
3053		< href="../../../resources/parrot.css"
3054		---
3055		> href="/parrot.css"
3056		17c17
3057		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">
3058		---
3059		> <img border=0 src="/parrot_logo.png" id="logo" alt="parrot">
3060		23c23
3061		< <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 20: Lexical Variables
3062		---
3063		> Untitled
	2565	< Copyright © 2002-2010, Parrot Foundation.
	2566	---
	2567	> Copyright © 2002-2009, Parrot Foundation.
	2568	diff -r parrot/docs/html/docs/pdds/pdd20_lexical_vars.pod.html parrot-trunk/docs/html/docs/pdds/pdd20_lexical_vars.pod.html
	2569	5c5
	2570	< <title>Parrot - Untitled</title>
	2571	---
	2572	> <title>Parrot - PDD 20: Lexical Variables</title>
	2573	23c23
	2574	< Untitled
	2575	---
	2576	> <a href="../../../html/index.html">Home</a> » <a href="../../../html/pdds.html">Parrot Design Documents (PDDs)</a> » PDD 20: Lexical Variables
3064	2577	312c312
3065		< <p><em>~~<a href="../../t/op/lexicals.t.html">t/op/lexicals.t</a>~~</em></p>
3066		---
3067		> <p><em>~~t/op/lexicals.t~~</em></p>
	2578	< <p><em>t/op/lexicals.t</em></p>
	2579	---
	2580	> <p><em><a href="../../t/op/lexicals.t.html">t/op/lexicals.t</a></em></p>
3068	2581	316c316
3069		< Copyright © 2002-2009, Parrot Foundation.
3070		---
3071		> Copyright © 2002-2010, Parrot Foundation.
3072		diff -r parrot-trunk/docs/html/docs/pdds/pdd21_namespaces.pod.html parrot/docs/html/docs/pdds/pdd21_namespaces.pod.html
3073		5c5
3074		< <title>Parrot - PDD 21: Namespaces</title>
3075		---
3076		> <title>Parrot - Untitled</title>
3077		7c7
3078		< href="../../../resources/parrot.css"
3079		---
3080		> href="/parrot.css"
3081		17c17
3082		< <img border=0 src="../../../resources/parrot_logo.png" id="logo" alt="parrot">