perl6-internals
[Top] [All Lists]

[svn:parrot-pdd] r30633 - trunk/docs/pdds

To: perl6-internals@perl.org
Subject: [svn:parrot-pdd] r30633 - trunk/docs/pdds
From: kjs@cvs.perl.org
Date: Fri, 29 Aug 2008 03:13:08 -0700 (PDT)
Delivered-to: mailing list perl6-all@perl.org
Delivered-to: perl6-all-poster@perl.org
Delivered-to: mailing list perl6-internals@perl.org
Delivered-to: perl6-internals@perl.org
List-help: <mailto:perl6-all-help@perl.org>
List-id: <perl6-all.perl.org>
List-id: <perl6-internals.perl.org>
List-post: <mailto:perl6-all@perl.org>
List-subscribe: <mailto:perl6-all-subscribe@perl.org>
List-unsubscribe: <mailto:perl6-all-unsubscribe@perl.org>
Mailing-list: contact perl6-all-help@perl.org; run by ezmlm
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


<Prev in Thread] Current Thread [Next in Thread>
  • [svn:parrot-pdd] r30633 - trunk/docs/pdds, kjs <=