Author: kjs Date: Tue Aug 26 04:27:55 2008 New Revision: 30569 Modified: trunk/docs/pdds/pdd19_pir.pod
Log: [pdd19] be a bit more precise in opcode names vs local var names vs sub names. Modified: trunk/docs/pdds/pdd19_pir.pod ============================================================================== --- trunk/docs/pdds/pdd19_pir.pod (original) +++ trunk/docs/pdds/pdd19_pir.pod Tue Aug 26 04:27:55 2008 @@ -62,8 +62,11 @@ Opcode names are not reserved words in PIR, and may be used as variable names. For example, you can define a local variable named C<print>. [See RT #24251] +Note that by using an opcode name as a local variable name, the variable will +I<hide> the opcode name, effectively making the opcode unusable. Opcode names +used as subroutine identifiers, on the other hand, will I<hide> that opcode. -PIR keywords, on the other hand, I<are> reserved, and cannot be used as +In contrast to opcode names, PIR keywords I<are> reserved, and cannot be used as identifiers. Some opcode names (C<if>, C<unless>) are, in fact, PIR keywords, which therefore cannot be used as identifiers.
