use an AUTOLOAD to auto-create PackingList visitors when needed.

Document visitors, at least partially.

1 files changed, 9 insertions, 1 deletions

diff --git a/usr.sbin/pkg_add/pod/OpenBSD::PackingList.pod b/usr.sbin/pkg_add/pod/OpenBSD::PackingList.pod
index 036a084d9fd..5c5794bf796 100644
--- a/usr.sbin/pkg_add/pod/OpenBSD::PackingList.pod
+++ b/usr.sbin/pkg_add/pod/OpenBSD::PackingList.pod
@@ -1,4 +1,4 @@
-$OpenBSD: OpenBSD::PackingList.pod,v 1.5 2005/09/19 09:30:28 espie Exp $
+$OpenBSD: OpenBSD::PackingList.pod,v 1.6 2007/04/29 10:52:15 espie Exp $
 
 =head1 NAME
 
@@ -34,6 +34,9 @@ OpenBSD::PackingList - C<pkg_add(1)> packing-list manipulations
     # processing packing-lists
     $p4->visit('method', @args);
 
+    # auto visit
+    $p4->method(@args);
+
     # signatures
     if ($p3->signature() eq $p4->signature()) {
     }
@@ -123,3 +126,8 @@ C<$plist-E<gt>pkgname()> retrieves a packing-list name (mandatory).
 C<$plist-E<gt>signature()> retrieves a packing-list full signature, composed
 of the package name and dependency information.
 
+C<$plist-E<gt>visit($method, @args)> is a visitor pattern, calling
+C<method(@args)> on each element of the packing-list in a specific order.
+
+As a feature, if C<OpenBSD::PackingElement-E<gt>can(method)>, 
+C<$plist-E<gt>method(@args)> will be turned into a visitor call automatically.