On Tue, 2004-01-20 at 16:17, Stas Bekman wrote: > I now more or less have an idea on how to solve the code usage problem.
Great! > What I don't have clear yet is the docs issue. Certainly you want to find the > method of class Apache::RequestRec in its the right manpage > (Apache::RequestRec). But $r has about 150 methods. Yes, this is a trickier question. Looking at other big projects, it seems like DBI and CGI have chosen the "one huge page" approach. This still works fairly well since they make careful use of headings in the POD. Ideally, I'd certainly like to see all of the methods available through $r documented in Apache::RequestRec, even if it does make the page big. Any idea if it would be bigger than DBI or not? > So my idea was to list all Apache::RequestRec methods in the > Apache::RequestRec manpage, but have the bodies of most of them spread across > Apache::RequestIO, etc, just like it is now. That's if you use the web > interface. It won't quite work for 'perldoc'. That would be my second choice if the one page is unmanageable. Which part doesn't work with perldoc? Just the actual links? - Perrin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
