Date: Tue, 28 Jun 2005 17:19:40 -0500 From: Greg Barniskis <nalists@scls.lib.wi.us> To: Joe Altman <fj@panix.com> Cc: Trey Sizemore <trey@fastmail.fm>, freebsd-questions@freebsd.org Subject: Re: Upgraded Perl; and lo, errors cause exim to fail Message-ID: <42C1CCFC.5090909@scls.lib.wi.us> In-Reply-To: <20050628220417.GA18375@panix.com> References: <20050628161027.GA21883@panix.com> <20050628170857.GF92129@keyslapper.net> <1119995578.19863.4.camel@salamander.thesizemores.net> <20050628220417.GA18375@panix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Altman wrote: > On Tue, Jun 28, 2005 at 05:52:58PM -0400, Trey Sizemore wrote: > >>When you say embedded, what do you mean? How do I go about reading the >>documentation so that I can find the correct syntax for the command? > > > You can look at the man page. There are two basic commands, outlined > in the man page: > > man perl-after-upgrade > [snip] Also, with this script and with most well-written perl scripts, modules, libraries, etc., you can do perldoc perl-after-upgrade to read the perl "pod" commentary that is literally embedded inside the perl code (making the documentation OS independent and inseparable from the script). In this case, result is the same as the man page. See also: perldoc perlpod for more information on embedded Perl documentation. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) <gregb at scls.lib.wi.us>, (608) 266-6348
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C1CCFC.5090909>