From d28ebecde48fa14623be7a09bf607426f095b6c1 Mon Sep 17 00:00:00 2001 From: Perl 5 Porters Date: Mon, 11 Mar 1996 07:12:18 +0000 Subject: Fix miscellaneous typos --- pod/perlmod.pod | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'pod/perlmod.pod') diff --git a/pod/perlmod.pod b/pod/perlmod.pod index 7a8431b15b..80a4036246 100644 --- a/pod/perlmod.pod +++ b/pod/perlmod.pod @@ -747,8 +747,8 @@ Generally you can delete the "eq 'FOO'" part with no harm at all. Let the objects look after themselves! Generally, avoid hardwired class names as far as possible. -Avoid $r->Class::func() where using @ISA=qw(... Class ...) and -$r->func() would work (see perlbot man page for more details). +Avoid $r-EClass::func() where using @ISA=qw(... Class ...) and +$r-Efunc() would work (see perlbot man page for more details). Use autosplit so little used or newly added functions won't be a burden to programs which don't use them. Add test functions to @@ -798,7 +798,7 @@ or nature of a variable. For example: $no_caps_here function scope my() or local() variables Function and method names seem to work best as all lowercase. -E.g., $obj->as_string(). +E.g., $obj-Eas_string(). You can use a leading underscore to indicate that a variable or function should not be used outside the package that defined it. @@ -814,7 +814,7 @@ export try to use @EXPORT_OK in preference to @EXPORT and avoid short or common names to reduce the risk of name clashes. Generally anything not exported is still accessible from outside the -module using the ModuleName::item_name (or $blessed_ref->method) +module using the ModuleName::item_name (or $blessed_ref-Emethod) syntax. By convention you can use a leading underscore on names to informally indicate that they are 'internal' and not for public use. -- cgit v1.2.1