# New Ticket Created by  Alin Iacob 
# Please include the string:  [perl #18780]
# in the subject line of all future correspondence about this issue. 
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=18780 >


As I read the PDDs I notice that some of them say 'perl' where it should really say 
'parrot' (remnants from the pre Parrot era?)
This patch clears some of the confusion.

--
Cheers,
Alin


-- attachment  1 ------------------------------------------------------
url: http://rt.perl.org/rt2/attach/43578/34673/b42705/pdd.patch

diff -ur parrot/docs/pdds/pdd02_vtables.pod fatbird/docs/pdds/pdd02_vtables.pod
--- parrot/docs/pdds/pdd02_vtables.pod  Fri Oct 18 21:33:09 2002
+++ fatbird/docs/pdds/pdd02_vtables.pod Sat Nov 30 14:41:00 2002
@@ -59,9 +59,9 @@
 
 =head1 DESCRIPTION
 
-All perl variables hide their guts behind a magic perl structure
-generally referred to as a PMC, or Perl Magic Cookie. Nothing outside
-the core of perl (in fact, nothing outside the data type's vtable
+All parrot variables hide their guts behind a magic parrot structure
+generally referred to as a PMC, or Parrot Magic Cookie. Nothing outside
+the core of parrot (in fact, nothing outside the data type's vtable
 routines) should infer anything about a PMC. (hence the Magic part)
 
 The first parameter to all of these should be the current interpreter.
@@ -71,7 +71,7 @@
 implementation of various object functions. This does mean, though,
 that you need to either know what functions are available and what
 they do, or have some method of finding out. It's faster if you know
-which vtable entry does what, so that's the method perl's using.
+which vtable entry does what, so that's the method parrot's using.
 
 The actual vtable structure contains pointers to functions that
 implement the methods for that particular vtable.  All pointers
diff -ur parrot/docs/pdds/pdd04_datatypes.pod fatbird/docs/pdds/pdd04_datatypes.pod
--- parrot/docs/pdds/pdd04_datatypes.pod        Tue Apr  2 10:08:43 2002
+++ fatbird/docs/pdds/pdd04_datatypes.pod       Sat Nov 30 14:50:10 2002
@@ -59,11 +59,11 @@
 
 =head1 ABSTRACT
 
-This PDD describes perl's known internal data types.
+This PDD describes parrot's known internal data types.
 
 =head1 DESCRIPTION
 
-This PDD details the primitive datatypes that the perl core knows how
+This PDD details the primitive datatypes that the parrot core knows how
 to deal with. These types are lower-level than what's presented to the
 perl programmer.
 
@@ -78,7 +78,7 @@
 
 =item Platform-native integer
 
-These are whatever size native integer was chosen at perl
+These are whatever size native integer was chosen at parrot
 configuration time. The C-level typedef C<IV> and C<UV> get you a
 platform-native signed and unsigned integer respectively.
 
@@ -128,7 +128,7 @@
 
 =item Platform native float
 
-These are whatever size float was chosen when perl was configured. The
+These are whatever size float was chosen when parrot was configured. The
 C level typedef C<NV> will get you one of these.
 
 =item Arbitrary precision decimal numbers
@@ -158,7 +158,7 @@
 
 =head2 String data types
 
-Perl has a single internal string form:
+Parrot has a single internal string form:
 
    struct perl_string {
      void *buffer;
@@ -189,7 +189,7 @@
 
 =item flags
 
-Flags indicating whatever. Bits 0-15 are reserved for perl, bits 16-23
+Flags indicating whatever. Bits 0-15 are reserved for parrot, bits 16-23
 for the encoding/decoding code, and the rest for the type code.
 
 =item characters
Only in fatbird/docs/pdds/: pdd04_datatypes.pod~
diff -ur parrot/docs/pdds/pdd05_opfunc.pod fatbird/docs/pdds/pdd05_opfunc.pod
--- parrot/docs/pdds/pdd05_opfunc.pod   Tue Apr  2 10:08:43 2002
+++ fatbird/docs/pdds/pdd05_opfunc.pod  Sat Nov 30 14:52:01 2002
@@ -65,7 +65,7 @@
 interpreter will call. Normally this is automatically generated.
 
 The I<inner function> is the code that gets directly executed when
-perl gets TIL-ified. If there is no I<inner function> for some reason,
+parrot gets TIL-ified. If there is no I<inner function> for some reason,
 then your opcode will likely run slower (as the interpreter would need
 to set up the registers and other stuff that would normally get
 stripped away for speed)
@@ -137,7 +137,7 @@
 
 =item STRING
 
-Indicates the item is a perl string pointer
+Indicates the item is a parrot string pointer
 
 =item PMC
 

Reply via email to