in reply to On Perl CPAN modules

Well, I find it hard to believe that the five minutes that it would take you to type perl -MCPAN -eshell followed by install HTTP::Request::Common would be longer than you reinventing everything that module calls, including getting it right for the general case. That's why I boggle sometimes at the "no module" crowd.

And even if you don't have good net access, I've seen entire CPAN disks on CD-ROM, so no net connection is required.

You also misinterpret Tom Christiansen. The point of PPT is not to reinvent Unix because he can. The point is to give Unix tools to the unwashed Windows masses, which he considers impoverished. Many of those programs use CPAN modules heavily, so it actually discredits your argument. {grin}

The problem with CGI.pm is not its size: it's that there's so many things to do to handle CGI in general. Every time I've seen something scaled down, it didn't handle something that would eventually have to be handled by adding more code, which already existed in CGI.pm. And CGI.pm is already very agressive at being a "compile as you go" module, minimizing startup cost.

OK, do you have any objections other than those to using CPAN modules? Bring them on. {grin}

-- Randal L. Schwartz, Perl hacker

Replies are listed 'Best First'.
RE: RE: On Perl CPAN modules
by strredwolf (Chaplain) on Oct 01, 2000 at 19:42 UTC
    What if you don't have ANYTHING but the bare distro? No money to buy a CD. No connection (I may be in class). Answer me that. $time{&to("install",$module)}=5 if(&$i{"had"}("internet connection"));

    About Tom: *WHAT?!?* Great, time to make a Linux distro...

    About CGI.pm: CGI.pm is a catch-all, and many people have told about it's problems both here, on other sites, and on dead-tree print (Linux Jornal comes to mind). From what I've seen, even with CGI.pm's minimization, it still takes a long time to compile, and it looks like the best thing to advoid on speed-critical scripts.

    Oh, yeah, now that you mention it: Module dependencies on modules. I'm getting confused over what GIMP::Perl wants, which needs PDL, which needs... well, it's a nice documentation problem which I wish was shifted over to program side. I'll love to have it so I can do a "perl Makefile.pl -print-needed-modules". Has that been solved? Will CPAN Modules have a INSTALL file in the archives? What about the moderate newbie (which I seem to be turning out to).

    --
    &$WolfSkunks({use Perl;}); do {$you};

[reply]
      Reading your posts, I am a little unclear as to your point of view. regarding your position on modules, is it: A. Internet access is difficult or near impossible, so by default, you're remanded to rolling your own, unless included with whatever distro you're running? B. You're a "purist", and regardless of internet connectivity, you'd prefer to do without? If you're answer is B, then why not politely tell us, "Thanks but this is how I feel", and move on. If it's A, then you've got options. Also, I'm having a hard time understanding where your sense of urgency fits in. I really can't comment on some of the points you make regarding specific modules and PPT, never having used them, but while criticizing them, remember that the folks who wrote these, did so primarily in their spare time, and provided them to the Perl community freely. Yes, there are problems, but rather than just complaining and becoming part of the problem, become a pro-active part of some solution, like submitting cohesive, accurate bug-reports to the respective maintainers of the software you're having problems with. Better yet, if you have the skills, time, etc., volunteer to help fix or modify the problematic code! Don't like GIMP::Perl docs? Write 'em! "Wishing" will accomplish nothing.
[reply]
[d/l]
[select]
        Actually, over the course of the posts here... if I *can* clarify:

        • I belive modules not to be the best thing out there. True, they can help out in a pinch, but somehow I'm feeling the general CPAN "tools" aren't quite specific enough, and I'd like coding it by hand anyway.
        • Well, that, and they're !*)#@( confusing -- there's a steep learning curve AFAIKT. Anyone got a FAQ on Perl Modules?
        • And of course, those module dependencies. Hmmm... I think I actually have a solution for that one.

        --
        &$WolfSkunks({use Perl;}); do {$you};

[reply]
      PS, I --'d your post because the beginning sounds more like, "if you were alone on a desert island, would you rather.....", than a question of real circumstance.
[reply]
RE: RE: On Perl CPAN modules
by princepawn (Parson) on Oct 04, 2000 at 17:54 UTC
    Actually, I find Cygwin to be an excellent unix layer for win32 use.

    But who wants windows... I just bought an iBook last night and the sucker rips... 366mhz and it completely leaves my dell 500mhz in the dust.

[reply]

In Section Meditations