Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re: Not Matt's Scripts

by princepawn (Parson)
on Aug 11, 2001 at 21:38 UTC ( #104161=note: print w/ replies, xml ) Need Help??


in reply to Not Matt's Scripts

I think it would be easy enough to post them here one by one and have us cobble up replacements.... it would give those chatter box vultures something to do besides philosophize about evolution and the origin of monogamy. :)

It might be very instructive to show before and after versions of the scripts.

Finally, CPAN has a scripts archive, though it isn't widely used. I would recommend writing modules which can be scripted via it's API instead of writing scripts proper.


Comment on Re: Not Matt's Scripts
Re: Re: Not Matt's Scripts
by davorg (Chancellor) on Aug 11, 2001 at 22:07 UTC
    It might be very instructive to show before and after versions of the scripts.

    You can do that easily enough at the moment by pulling down my versions and comparing them with Matt's. I might consider putting Matt's versions in my distribution as a lesson to us all, but I think he's quite protective on things like that.

    Finally, CPAN has a scripts archive, though it isn't widely used.

    The deputy librarian of CPAN has already shown great interest in these scripts. They will, no doubt, appear there in due course.

    I would recommend writing modules which can be scripted via it's API instead of writing scripts proper.

    There's a chance that something like that might happen much later. The problem is that Matt's scripts are so popular precisely because they are so easy to use. There's no need to install modules from CPAN or do anything that a novice webmaster might find confusing. If these scripts are to find any kind of popularity they have to be just as simple to use.

    --
    <http://www.dave.org.uk>

    Perl Training in the UK <http://www.iterative-software.com>

      Just write the functionality of the script as a module and put "standard usage" of it at the end like:

      package main; require File::Basename; File::Basename->import( qw(basename) ); if( &basename( $0 ) eq &basename( __FILE__ ) ) { require CGI; my $q= CGI->new(); # ... }
      that way you can make one file that is both a module and an all-in-one CGI script. This might even help the modulephobic slowly learn to like modules. (:

              - tye (but my friends call me "Tye")
        I've used a similar trick in the past, but rather than checking basename(), it's "unless ( caller ) { ...}", which seems to be equivalent.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://104161]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (7)
As of 2014-08-01 10:42 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Who would be the most fun to work for?















    Results (4 votes), past polls