summaryrefslogtreecommitdiff
path: root/pod/perlmodlib.PL
diff options
context:
space:
mode:
Diffstat (limited to 'pod/perlmodlib.PL')
-rw-r--r--pod/perlmodlib.PL4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlmodlib.PL b/pod/perlmodlib.PL
index 969dde92f7..a574543e49 100644
--- a/pod/perlmodlib.PL
+++ b/pod/perlmodlib.PL
@@ -1070,8 +1070,8 @@ the module after __END__ either using AutoSplit or by saying:
Does your module pass the 'empty subclass' test? If you say
C<@SUBCLASS::ISA = qw(YOURCLASS);> your applications should be able
to use SUBCLASS in exactly the same way as YOURCLASS. For example,
-does your application still work if you change: C<$obj = new YOURCLASS;>
-into: C<$obj = new SUBCLASS;> ?
+does your application still work if you change: C<< $obj = YOURCLASS->new(); >>
+into: C<< $obj = SUBCLASS->new(); >> ?
Avoid keeping any state information in your packages. It makes it
difficult for multiple other packages to use yours. Keep state