Anonymous avatar Anonymous committed 00301ed

Some updates to the main readme.

Comments (0)

Files changed (1)

 Once you have checked out a copy of pynie, build it as follows:
 
   $ cd pynie
-  $ setup.py build
+  $ python setup.py build
 
 This will create a "pynie.pbc" parrot bytecode executable in the
 current directory.   Pynie doesn't currently have a "install"
 
 To invoke pynie on a Python program from a shell prompt, use:
 
-  $ parrot pynie.pbc foo.py
+  $ ./pynie foo.py
 
 To run interactively, entering single-line statements:
 
-  $ parrot pynie.pbc
+  $ ./pynie
 
 Note that pynie's interactive mode is not yet up to spec
 with Python's interactive mode (it doesn't handle blocks yet).
 
 To run pynie's test suite:
 
-  $ setup.py test
+  $ python setup.py test
 
 To display the parse tree, add the "--target=parse" option:
 
-  $ parrot pynie.pbc --target=parse foo.py
+  $ ./pynie --target=parse foo.py
 
 Or, to display the abstract syntax tree, the opcode syntax tree,
 or the generated PIR code, use "--target=PAST", "--target=POST",
 
 =head2 Files
 
-The "top" file for the parser is F<pynie.pir> which is used to
-create the F<pynie.pbc> file.  It initializes the overall
-parsing system and registers the parser as a Parrot "Pynie" compiler.
+The "top" file for the parser is F<pynie.pir> which is used to create
+the F<pynie.pbc> file and F<pynie> executable.  It initializes the
+overall parsing system and registers the parser as a Parrot "Pynie"
+compiler.
 
 The other files needed for the compiler are in the F<src/> subdirectory.
 
 and handed off to the next compilation phases (PAST->POST->PIR)
 
 The PIR files in F<src/builtins> are included as part of
-compiling F<pynie.pir> to produce F<pynie.pbc>.
+compiling F<pynie.pir> to produce F<pynie.pbc> and F<pynie>.
 
 The F<pynie.pbc> file can also be used to compile Python code
 from within PIR:
 Patches/bugs/suggestions can be sent to
 <https://launchpad.net/pynie/+filebug>.
 
-=head1 AUTHOR
-
-Patrick Michaud <pmichaud@pobox.com> is the current author and
-maintainer.
-
 =cut
 
 ## vim: expandtab sw=4
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.