From: Rafael Garcia-Suarez <rgarciasuarez@gmail.com>
Date: Mon, 25 Sep 2006 13:28:24 +0000 (+0000)
Subject: Remove three X<...> that cannot be handled by pod2text currently
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=1c540e1c282c205aa9027fe0147eccdd12cfba93;p=p5sagit%2Fp5-mst-13.2.git

Remove three X<...> that cannot be handled by pod2text currently
(spotted by David Landgren)

p4raw-id: //depot/perl@28890
---

diff --git a/pod/perlref.pod b/pod/perlref.pod
index 65abf22..1781775 100644
--- a/pod/perlref.pod
+++ b/pod/perlref.pod
@@ -330,7 +330,6 @@ However, a "simple scalar" includes an identifier that itself uses method
     print $$$$refrefref;
 
 =item 2.
-X<${}> X<@{}> X<%{}>
 
 Anywhere you'd put an identifier (or chain of identifiers) as part of a
 variable or subroutine name, you can replace the identifier with a
@@ -367,7 +366,6 @@ called %hashref, not dereferencing through $hashref to the hash
 it's presumably referencing.  That would be case 3.
 
 =item 3.
-X<autovivification> X<< -> >> X<arrow>
 
 Subroutine calls and lookups of individual array elements arise often
 enough that it gets cumbersome to use method 2.  As a form of
@@ -405,7 +403,6 @@ Well, okay, not entirely like C's arrays, actually.  C doesn't know how
 to grow its arrays on demand.  Perl does.
 
 =item 4.
-X<encapsulation>
 
 If a reference happens to be a reference to an object, then there are
 probably methods to access the things referred to, and you should probably