Author: cotto
Date: Fri Sep 5 23:19:14 2008
New Revision: 30810
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
trunk/docs/pdds/pdd09_gc.pod
trunk/docs/pdds/pdd19_pir.pod
trunk/docs/pdds/pdd27_multiple_dispatch.pod
Log:
[pdd] make non-draft PDDs pass pdd_format.t
Modified: trunk/docs/pdds/pdd07_codingstd.pod
==============================================================================
--- trunk/docs/pdds/pdd07_codingstd.pod (original)
+++ trunk/docs/pdds/pdd07_codingstd.pod Fri Sep 5 23:19:14 2008
@@ -987,6 +987,10 @@
or C<is_perl_exemption()>). One can use wildcards in the list to exempt,
for example, all files under a given directory.
+=head1 REFERENCES
+
+none
+
=cut
# Local Variables:
Modified: trunk/docs/pdds/pdd09_gc.pod
==============================================================================
--- trunk/docs/pdds/pdd09_gc.pod (original)
+++ trunk/docs/pdds/pdd09_gc.pod Fri Sep 5 23:19:14 2008
@@ -557,9 +557,9 @@
For PMCs and Buffers to be collected properly, you must set the appropriate
flags on them. Directly manipulating these flags is not recommended because
-the exact values can be changed over time. A series of macros have been created
-in F<include/parrot/pobject.h> that set and check for these flags. Always use
-these provided macros when you need to test or set these flags.
+the exact values can be changed over time. A series of macros have been
+created in F<include/parrot/pobject.h> that set and check for these flags.
+Always use these provided macros when you need to test or set these flags.
=over 4
Modified: trunk/docs/pdds/pdd19_pir.pod
==============================================================================
--- trunk/docs/pdds/pdd19_pir.pod (original)
+++ trunk/docs/pdds/pdd19_pir.pod Fri Sep 5 23:19:14 2008
@@ -65,8 +65,8 @@
Note that by using an opcode name as a local variable name, the variable will
I<hide> the opcode name, effectively making the opcode unusable.
-In contrast to opcode names, PIR keywords I<are> reserved, and cannot be used
as
-identifiers. Some opcode names are, in fact, PIR keywords, which therefore
+In contrast to opcode names, PIR keywords I<are> reserved, and cannot be used
+as identifiers. Some opcode names are, in fact, PIR keywords, which therefore
cannot be used as identifiers.
The following are PIR keywords, and cannot be used as identifiers:
@@ -1282,6 +1282,10 @@
N/A
+=head1 REFERENCES
+
+N/A
+
=cut
__END__
Modified: trunk/docs/pdds/pdd27_multiple_dispatch.pod
==============================================================================
--- trunk/docs/pdds/pdd27_multiple_dispatch.pod (original)
+++ trunk/docs/pdds/pdd27_multiple_dispatch.pod Fri Sep 5 23:19:14 2008
@@ -111,8 +111,8 @@
Return an array of matching candidates, sorted from best matching to worst
matching, for a passed in signature. The signature passed in is a simple type
-string for the signature ('P' for PMC, 'I' for integer, 'N' for number, and 'S'
-for string).
+string for the signature ('P' for PMC, 'I' for integer, 'N' for number, and
+'S' for string).
=item get_iter
@@ -146,8 +146,8 @@
Return an array of matching candidates, sorted from best matching to worst
matching, for a passed in signature. If the signature passed in is an array of
PMCs, the types are extracted from the types of the array elements. If the
-signature passed in is a simple type string for the signature ('P' for PMC, 'I'
-for integer, 'N' for number, and 'S' for string), the types are matched as
+signature passed in is a simple type string for the signature ('P' for PMC,
+'I' for integer, 'N' for number, and 'S' for string), the types are matched as
simple types.
=back
