Author: particle Date: Wed Dec 28 17:47:56 2005 New Revision: 10755 Modified: trunk/docs/debug.pod trunk/docs/glossary.pod trunk/docs/native_exec.pod Log: #37520: [TODO] rename library files from .imc to .pir update the last few docs
Modified: trunk/docs/debug.pod ============================================================================== --- trunk/docs/debug.pod (original) +++ trunk/docs/debug.pod Wed Dec 28 17:47:56 2005 @@ -72,7 +72,7 @@ different objects over the lifetime of t =head1 PIR AND PASM CODE -Let's say you have written (or generated) a huge .pasm or .imc file. It's not +Let's say you have written (or generated) a huge .pasm or .pir file. It's not working. You'd like some help in figuring out why. =head2 pdb @@ -91,7 +91,7 @@ file). It is not strictly necessary, but bytecode this way. Let's say your file is named C<test.pasm>. (Note: these instructions will also -work if you use C<test.imc> everywhere C<test.pasm> occurs.) +work if you use C<test.pir> everywhere C<test.pasm> occurs.) Step 1: Generate the .pbc file with extra debugging information. Modified: trunk/docs/glossary.pod ============================================================================== --- trunk/docs/glossary.pod (original) +++ trunk/docs/glossary.pod Wed Dec 28 17:47:56 2005 @@ -172,7 +172,7 @@ L<http://oss.software.ibm.com/icu/index. Parrot InterMediate Code, or another name for PIR. A convention once arose to name input files to IMCC with the extension ".imc", so the name IMC became -synonymous with PIR. +synonymous with PIR. This file extension has since been deprecated. See also L<"IMCC">, L<"PIR">. Modified: trunk/docs/native_exec.pod ============================================================================== --- trunk/docs/native_exec.pod (original) +++ trunk/docs/native_exec.pod Wed Dec 28 17:47:56 2005 @@ -16,7 +16,7 @@ engine and a precompiled Parrot program Generating a native executable is done in three steps: building a packfile, assembling a native object, and then linking the native executable. -The packfile is generated in the standard way from .imc or .pasm source by IMCC. +The packfile is generated in the standard way from .pir or .pasm source by IMCC. For a program in myprog.pasm: ./parrot -o myprog.pbc myprog.pasm
