Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.)
      • 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.

        This doesn't contradict having the web-server being able to do what you wrote + other stuff (e.g. handle regular static+dynamic HTML pages).

        However, the general line is to avoid including new modules, if they don't relate to core functionality.

        As Perl is the language of choice for CGI scripts, a web-server seems to me a pretty natural candidate for "core functionality". Furthermore, the Net is becoming *more* important over time, not less, so having a core module that can serve HTML seems pretty basic to me, nowdays. I agree this wasn't the case in the past, but IMHO this is the case now.