I won't argue about perldoc being equally bad on all platforms, but I will add that I particularly like it WRT documenting my own scripts and modules. In our environment, we distribute executables and scripts but there is no provision for documenting anything. By putting something in the code itself, I can always 'perldoc <script.pl>' or 'perldoc <module>' to get *some* kind of documentation. Far better than having to study the code and try to figure out what I meant it to do when I wrote it. ;)
-- Hank Barta At The Hull Group, Chicago (312) 655-4636 -----Original Message----- From: Neil Kandalgaonkar [mailto:[EMAIL PROTECTED]] Sent: Monday, October 08, 2001 1:32 AM To: Jeremy Wadsack Cc: [EMAIL PROTECTED]; Activeperl (E-mail) Subject: Re: Perl Editor On Fri, Oct 05, 2001 at 09:57:23AM -0700, Jeremy Wadsack wrote: > But maybe that's because I don't know enough about perldoc. Heh. perldoc is a revolting hack (ask the people who wrote it). However, it does work *equally* badly on all platforms. :) On the other hand it's a nice shortcut for FAQs and especially builtin functions. (perldoc -tf -X, for example. Note that -X is NOT a command line switch there.). > Thank you for the perldoc tip. I might have to 'man perldoc' some day > soon! perldoc perldoc you mean... :) -- Neil Kandalgaonkar, ActiveState ASPN - ActiveState Programmer Network http://ASPN.ActiveState.com/ _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/activeperl _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/activeperl
