Author: jkeenan Date: Mon May 21 19:53:55 2007 New Revision: 18617 Modified: trunk/docs/tests.pod
Log: Following further discussion in RT 43008: In sections relating to testing of Perl 5 components, s/executable/program/g. Modified: trunk/docs/tests.pod ============================================================================== --- trunk/docs/tests.pod (original) +++ trunk/docs/tests.pod Mon May 21 19:53:55 2007 @@ -141,9 +141,9 @@ At the present time most, if not all, of the programs used to configure, build and install Parrot are written in Perl 5. These programs take the form of -executable files (F<*.pl>) and Perl modules (F<*.pm>) holding subroutines and -other variables imported into the executable files. Examples of such -executable files can be found under F<tools/>; examples of such Perl modules +program files (F<*.pl>) and Perl modules (F<*.pm>) holding subroutines and +other variables imported into the program files. Examples of such +program files can be found under F<tools/>; examples of such Perl modules can be found under F<lib/Parrot/>. All of these Perl 5 components ought to be tested. Fortunately, over the last @@ -160,7 +160,7 @@ =item b -Those subroutines are then imported back into the executable file. +Those subroutines are then imported back into the program file. =item c
