diff options
| author | chromatic <chromatic@wgz.org> | 2006-09-01 02:12:45 -0700 |
|---|---|---|
| committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2006-09-04 12:41:39 +0000 |
| commit | 63acfd0033368edc5dd21a89732267e5921511f1 (patch) | |
| tree | 1682996f5aefdbfe31dbba57de31bcaf806124fc /pod/perlmodlib.PL | |
| parent | ee6b43cc19efb39ed8a2fdad01d701e59dbdd946 (diff) | |
| download | perl-63acfd0033368edc5dd21a89732267e5921511f1.tar.gz | |
Re: AW: [PATCH pod/*] Use Direct Object Constructor Calls
Message-Id: <200609010912.46314.chromatic@wgz.org>
p4raw-id: //depot/perl@28778
Diffstat (limited to 'pod/perlmodlib.PL')
| -rw-r--r-- | pod/perlmodlib.PL | 4 |
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 |