All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

The goal is to make it possible to include Pod::Webserver and the podwebserver script in the Perl core.

If you're going to include a webserver in core, why limit it to serving PODs? Why not have a full blown static+CGI+whatever webserver? Why should the Python guys have [python.org] all [python.org] the [python.org] fun [python.org]?

I imagine that the goal is to have browser-accessible standalone documentation straight after installation. In this case, it makes sense to have this new module in the core. However, the general line is to avoid including new modules, if they don't relate to core functionality. (For example, we might include Module::Build in the core, but I really don't think that LWP or an XML parser should go in.)

Pod::Webserver would already include a web server in core. All that’s being argued for is to make this web server sufficiently decoupled from Pod::Webserver that it could be used for other things.

I think that’s a very sensible suggestion, myself – if only because people are going to layer horrible hacks onto Pod::Webserver to use it for other web serving purposes, much the way I am currently abusing CGI.pm to generate XML and sloshing around in its guts to get URL generation, because unl

...people are going to layer horrible hacks onto Pod::Webserver to use it for other web serving purposes...

Seems unlikely. The code is mindlessly simple. It order to use it for anything else, you'd pretty much have to rewrite the HTTP::* modules, in which case you might as well just install the HTTP::* modules.