Author: coke
Date: Wed May 30 08:58:47 2007
New Revision: 18689

Modified:
   trunk/   (props changed)
   trunk/docs/intro.pod
   trunk/docs/parrot.pod
   trunk/docs/porting_intro.pod

Log:
[docs]
- remove some old-style PIR
- can't compile from pir to pasm anymore
- cleanup



Modified: trunk/docs/intro.pod
==============================================================================
--- trunk/docs/intro.pod        (original)
+++ trunk/docs/intro.pod        Wed May 30 08:58:47 2007
@@ -133,7 +133,8 @@
   perl Configure.pl
 
 Once this is complete, run the C<make> program (sometimes called C<nmake> or
-C<dmake>).  This should complete, giving you a working Parrot executable.
+C<dmake> or C<gmake>).  This should complete, giving you a working Parrot
+executable.
 
 Please report any problems that you encounter while building Parrot so the
 developers can fix them. You can do this by sending a message to
@@ -174,7 +175,6 @@
 
   .sub main
       print "Hello world!\n"
-      end
   .end
 
 Then run it by typing:
@@ -188,8 +188,7 @@
 follow make up a subroutine named C<main>, until a C<.end> is encountered. The
 second line contains the C<print> instruction. In this case, we are calling the
 variant of the instruction that accepts a constant string. The assembler takes
-care of deciding which variant of the instruction to use for us. The third line
-contains the C<end> instruction, which causes the interpreter to terminate.
+care of deciding which variant of the instruction to use for us.
 
 =head2 Using registers
 
@@ -199,7 +198,6 @@
   .sub main
       set S0, "Hello world!\n"
       print S0
-      end
   .end
 
 Here we have stated exactly which register to use. However, by
@@ -210,7 +208,6 @@
   .sub main
       $S0 = "Hello world!\n"
       print $S0
-      end
   .end
 
 To make PIR even more readable, named registers can be used. These are later
@@ -220,7 +217,6 @@
       .local string hello
       hello = "Hello world!\n"
       print hello
-      end
   .end
 
 The C<.local> directive indicates that the named register is only needed inside
@@ -231,17 +227,6 @@
 
 =head2 PIR vs. PASM
 
-PIR can be turned into PASM by running:
-
-  parrot -o hello.pasm hello.pir
-
-The PASM for the final example looks like this:
-
-  _main:
-      set S30, "Hello world!\n"
-      print S30
-      end
-
 PASM does not handle register allocation or provide support for named
 registers.  It also does not have the C<.sub> and C<.end> directives, instead
 replacing them with a label at the start of the instructions.
@@ -275,7 +260,6 @@
       print " squares is "
       print total
       print ".\n"
-      end
   .end
 
 PIR provides a bit of syntactic sugar that makes it look more high level than
@@ -352,9 +336,6 @@
 
       inc i
       if i <= 10 goto loop
-
-      # That's it.
-      end
   .end
 
 The first line, C<.param int n>, specifies that this subroutine takes one

Modified: trunk/docs/parrot.pod
==============================================================================
--- trunk/docs/parrot.pod       (original)
+++ trunk/docs/parrot.pod       Wed May 30 08:58:47 2007
@@ -120,8 +120,8 @@
 
 Parrot compiles and runs on a large number of platforms, including all common
 ones. The Parrot team is committed to supporting the following combinations as
-"core platforms": Linux (x86), Cygwin, Win32, Tru64, OpenVMS (Alpha), Solaris
-(Sparc), FreeBSD (x86).
+"core platforms": Linux (x86), Win32, OS X (x86 and PPC), Cygwin, Tru64,
+OpenVMS (Alpha), Solaris (Sparc), FreeBSD (x86).
 
 =head2 Authors
 
@@ -131,13 +131,16 @@
 
 =over 4
 
-=item * Chip Salzenberg (C<[EMAIL PROTECTED]>) is the chief architect.  The 
mental
-institution he escaped from to accept the role is still searching for him.
+=item * Allison Randal is the chief architect.
+
+=item * Chip Salzenberg (C<[EMAIL PROTECTED]>) was the second chief architect.
 
 =item * Dan Sugalski (C<[EMAIL PROTECTED]>) was the chief architect for the 
first
 I<5 years> of the project.  Parrot is largely his brainchild.
 
-=item * Leopold Toetsch (C<[EMAIL PROTECTED]>) is the current release manager.
+=item * Leopold Toetsch (C<[EMAIL PROTECTED]>) was the release manager for some
+time. This position is currently rotated through several members of the
+project team.
 
 =item * Simon Cozens, Jeff Goff and Steve Fink were the release managers 
 for releases 0.0.1 - 0.0.4, 0.0.5 - 0.0.8, and 0.0.9 - 0.0.11 respectively.
@@ -154,12 +157,12 @@
 
 =over 4
 
+=item * L<http://www.parrotcode.org/>
+
 =item * L<http://dev.perl.org/>
 
 =item * L<http://svn.perl.org/>
 
-=item * L<http://www.parrotcode.org/>
-
 =back
 
 for more information.

Modified: trunk/docs/porting_intro.pod
==============================================================================
--- trunk/docs/porting_intro.pod        (original)
+++ trunk/docs/porting_intro.pod        Wed May 30 08:58:47 2007
@@ -62,6 +62,9 @@
 adding support may be possible with relatively little effort.  Implementing a
 novel JIT core from scratch is a substantial undertaking.
 
+Also note that some changes may be required based on OS as well. (e.g.:
+OS X/i386 vs. Linux/i386; OS X/i386 doesn't currently work.)
+
 =head2 References
 
 =over 4

Reply via email to