Author: kjs Date: Fri Aug 29 03:13:05 2008 New Revision: 30633 Modified: trunk/docs/pdds/pdd19_pir.pod
Log: [pdd19] remove a previously added line of mine which I no longer understand myself. Something about subroutine identifiers and hiding opnames. Modified: trunk/docs/pdds/pdd19_pir.pod ============================================================================== --- trunk/docs/pdds/pdd19_pir.pod (original) +++ trunk/docs/pdds/pdd19_pir.pod Fri Aug 29 03:13:05 2008 @@ -63,8 +63,7 @@ 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. +I<hide> the opcode name, effectively making the opcode unusable. In contrast to opcode names, PIR keywords I<are> reserved, and cannot be used as identifiers. Some opcode names are, in fact, PIR keywords, which therefore