We should rename all the PDDs to be consistent. I propose:
old name new name title
-------------- -------------------- --------------------------------------------
pdd0.pod => pdd00_pdd.pod Perl Design Documents
pdd1.pod => pdd01_overview.pod A high-level overview of the perl system
pdd2.pod => pdd02_vtables.pod Common vtable format for all variables
pdd3?? ?? ??
pdd4.pod => pdd04_datatypes.pod Perl's internal data types
pdd5.pod => pdd05_opfunc.pod Opcode Function specs
pdd6.pod => pdd06_pasm.pod Parrot assembly language
pdd7.pod => pdd07_codingstd.pod Conventions and Guidelines for Perl
Source Code
pdd8?? ?? ??
pdd09_gc.pod => pdd09_gc.pod Garbage Collection and Dead Object Detection
--Josh
At 23:03 on 03/05/2002 GMT, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 05, 2002 at 09:38:37AM -0500, Bryan C. Warnock wrote:
> > On Tuesday 05 March 2002 05:06, Simon Cozens wrote:
>
> > > As usual, if there's anything that you think REALLY MUST HAPPEN before
> > > release, speak now or forever hold thy peace.
> >
> > A quick run through the docs/README/etc to make sure they are up-to-date.
>
> Thanks for reminding me of something I meant to e-mail a few days ago
> [before I got swept up with perl 5.7.3. Please test perl 5.7.3 with anything
> you don't want 5.8 to choke on. Which is probably everything you use :-)]
>
> PDD 2 is truncated. It ends:
>
> Returns a pointer to the beginning of currently "OK" data; the type of
> this data must be determined by examining the PMCs C<type>. This must
> only be used by other vtable functions inside the core, and must never
> be used if the PMC is of a type defined by a user outside the core,
> unless you know what you're doing. (eg, comparing C<get_value>s from two
> PMCs of the same type, or C<set_value(PMC1,get_valu
>
> Where are PDDs 3 and 8?
>
> PDD5 has a truncated sentence at the end of =head1 Assembly syntax
>
> String and integer constants don't need to be put in a separate
>
> Nicholas Clark
> --
> Even better than the real thing: http://nms-cgi.sourceforge.net/
