Boris Zentner wrote: [...]
lets suppose that we use mp2doc to search. Or even better patch perldoc.
I doubt it's a good idea. Imagine every project trying to add their things and flags into perldoc. You can be sure that perldoc maintainers will say 'no'.
Besides it won't help all those with the older perls. [...]
whenever I think of it, my conclusion is to use one big page for every package.
mp2doc Apache::RequestRec read
should load Apache::RequestRec.pod and jump to the read description of that method.
that's a sugar feature. I won't worry about it now.
it's possible that we will need to have different solutions for command line and web utils, unless we throw all methods into one manpage.
...just brainstorming aloud here, throw your ideas please ...
choose the flags in a way that did not overlap with perldoc.
You can never know which flags will be used by perldoc in the future. Unless you safely prefix them with something like -mp2 as you have mentioned ealier. if mp2doc is used only for mp2 docs then the need for the special flag disappears. And you can do:
mp2doc Apache::RequestRec
or
mp2doc -f read # ala perldoc -f
and it will either show you the page or ask you which one you want to see if there are more than one. Of course:
mp2doc -f Apache::RequestRec::read
should show you the right page right away
but again, this is all sugar features and I won't worry about them now, as they can work no matter how the methods are spread across the manpages.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
