Sorry, my brane is elsewhere. This one has the patch attached. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ That which stirs me, stirs everything. -- Squonk Opera, "Spoon"
--- pod/perlboot.pod 2001/02/05 01:53:43 1.1 +++ pod/perlboot.pod 2001/02/05 01:57:50 @@ -790,9 +790,13 @@ For more information, see L<perlobj> (for all the gritty details about Perl objects, now that you've seen the basics), L<perltoot> (the -tutorial for those who already know objects), L<perlbot> (for some -more tricks), and books such as Damian Conway's excellent I<Object -Oriented Perl>. +tutorial for those who already know objects), L<perltootc> (dealing +with class data), L<perlbot> (for some more tricks), and books such as +Damian Conway's excellent I<Object Oriented Perl>. + +Some modules which might prove interesting are Class::Accessor, +Class::Class, Class::Contract, Class::Data::Inheritable, +Class::MethodMaker and Tie::SecureHash =head1 COPYRIGHT --- pod/perltoot.pod 2001/02/05 01:52:03 1.1 +++ pod/perltoot.pod 2001/02/05 01:57:46 @@ -425,6 +425,10 @@ Notice how there's no memory to deallocate in the destructor? That's something that Perl takes care of for you all by itself. +Alternatively, you could use the Class::Data::Inheritable module from +CPAN. + + =head2 Accessing Class Data It turns out that this is not really a good way to go about handling @@ -1749,6 +1753,16 @@ L<perltie>, and L<overload>. + +L<perlboot> is a kinder, gentler introduction to object-oriented +programming. + +L<perltootc> provides more detail on class data. + +Some modules which might prove interesting are Class::Accessor, +Class::Class, Class::Contract, Class::Data::Inheritable, +Class::MethodMaker and Tie::SecureHash + =head1 AUTHOR AND COPYRIGHT --- pod/perltootc.pod 2001/02/05 01:43:39 1.1 +++ pod/perltootc.pod 2001/02/05 01:51:27 @@ -74,6 +74,15 @@ scope, or you can limit direct data access exclusively to the methods implementing those attributes. +=head1 Class Data in a Can + +One of the easiest ways to solve a hard problem is to let someone else +do it for you! In this case, Class::Data::Inheritable (available on a +CPAN near you) offers a canned solution to the class data problem +using closures. So before you wade into this document, consider +having a look at that module. + + =head1 Class Data as Package Variables Because a class in Perl is really just a package, using package variables @@ -1302,7 +1311,8 @@ L<perltoot>, L<perlobj>, L<perlmod>, and L<perlbot>. -The Tie::SecureHash module from CPAN is worth checking out. +The Tie::SecureHash and Class::Data::Inheritable modules from CPAN are +worth checking out. =head1 AUTHOR AND COPYRIGHT @@ -1334,4 +1344,4 @@ =head1 HISTORY -Last edit: Fri May 21 15:47:56 MDT 1999 +Last edit: Sun Feb 4 20:50:28 EST 2001 --- pod/perlobj.pod 2001/02/05 02:04:18 1.1 +++ pod/perlobj.pod 2001/02/05 02:04:30 @@ -559,8 +559,8 @@ =head1 SEE ALSO -A kinder, gentler tutorial on object-oriented programming in Perl -can be found in L<perltoot> and L<perltootc>. You should also check -out L<perlbot> for other object tricks, traps, and tips, as well -as L<perlmodlib> for some style guides on constructing both modules -and classes. +A kinder, gentler tutorial on object-oriented programming in Perl can +be found in L<perltoot>, L<perlbootc> and L<perltootc>. You should +also check out L<perlbot> for other object tricks, traps, and tips, as +well as L<perlmodlib> for some style guides on constructing both +modules and classes.
