Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re: de-inventing the wheel (discussion)

by Masem (Monsignor)
on Jun 21, 2001 at 19:03 UTC ( [id://90391]=note: print w/replies, xml ) Need Help??


in reply to de-inventing the wheel (discussion)

I know you've discussed woes at your place of work before, Dep, and it sounds like they have poor IT support; unforunately, there's not much you can do to change their minds about how they feel about updating and the like. The best that you can do is that when you think an update is needed is to compile a list of advantages and deterents to the upgrade, and make your case as clear as possible at the same time as respecting their concerns. Given them cost/time/diskspace/memory estimates, make it as easy as possible for them to yea or nay it without too much additional material.

In this specific case, if you have a site, I'm surprised that you don't also have a testbed server that isn't publically available. What I would do is to copy the current batch of scripts to a testbed system, install the perl tools that you need, and see which scripts fail to work. Optionally, in the case that you're talking about, if you think that access() and sub() is used throughout the CGI scripts given (and given some of the code that you have shown, I doubt that your coworkers have used these), then simply do a grep for "use CGI" and "access" or "sub", and check to see how many instances that you hit; if it's more than a dozen or so out of 200 files, then you might have some concern, but anything on the low end is easy to fix. (I'd want to go one step further, saying using a sed-like tool to simply convert all 'access' to 'Access' and 'sub' to 'Sub', but that's not the best answer if you don't know what context they are used in, eg is it sub the function or sub the keyword?).

But if you say that all the scripts simply have #!/usr/local/bin/perl instead of a specific version, and you want to have two different versions of perl installed, it's rather easy to use sed to fix this problem in all 200 scripts automagically. Simply force existing scripts to 5.005, and then have 5.6 around as well; make sure that 5.6's @INCs are separated from 5.005's @INCs as well to avoid module contaimination. Nothing existing breaks with this, and you can get 5.6 stuff out the door as well.


Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

Replies are listed 'Best First'.
Re: Re: de-inventing the wheel (discussion)
by deprecated (Priest) on Jun 21, 2001 at 19:20 UTC
    These things I understand, Masem. I was more using my work as an example, and posing the question to people here.

    I hear from a lot of the people here, even, a very ingrained "upgrading is bad" vibe. Like if there isnt a very serious reason to upgrade, dont do it. Don't make use of new features in code (even if the API includes it), dont use modules, and so on.

    I feel it is unprofessional, unwise, and just plain bad coding to do so, and I was hoping to get some response from the people here that code this way.

    Perhaps I should post another piece of code with our all over it to draw the "dont use that"'ers out of the woodwork. :p

    brother dep.

    --
    Laziness, Impatience, Hubris, and Generosity.

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others perusing the Monastery: (4)
As of 2024-03-28 08:40 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found