I'm just trying to keep from using any non-standard modules. Makes it alot easier for maintanance.
Errr...come again? So, you're saying that you'd rather throw away the thousands-of-eyes testing for a CPAN module to bypass having to type 'perl -MCPAN -eshell' at the command line? To each his own, I suppose...
| [reply] [Watch: Dir/Any] |
Well, no, I'd also like to learn why my code is failing, so I become a better programmer. And it's more a matter of training our end-user support staff to type "perl -MCPAN -eshell" at the command line, and making sure they do it right. That tends to make my boss wonder why we don't just do it in VB or some other M$ product, since that's easier on our $7.50 an hour desk monkeys. With high turnover in that department, we like to keep our training needs to a minimum. If it dosen't come with the core ActivePerl distro it's a drawback for us.
Also, Many of my programs are installed at remote locations for beaming data back to the mothership. We don't have any geeks out there when things break, and it's alot easier to tell a 56 year-old gardening expert to just double click a file and everything will be OK.
I have been very succesful at slipping perl in the back door of this company by crafting solutions that were more stable and required less maintenance than their previous VB versions. Training our help desk to use CPAN really isn't part of the plan.
| [reply] [Watch: Dir/Any] |
If we're talking about just playing around with something to learn how it works, I'm all for rolling my own stuff so I can see how complicated something is, or expand theory, or just for fun.
You're talking about a production application here. The more robust the solution, the better. Fewer headaches for you. Since you don't like CPAN on the production server, and you're running NT, why not take advantage of the native Win32 functions for playing with INI files. GetPrivateProfileString is the function under Windows, if my memory still works.
There was a recent meditation on using the Win32::API module.
| [reply] [Watch: Dir/Any] |
With high turnover in that department, we like to keep our training needs to a minimum. If it dosen't come with the core ActivePerl distro it's a drawback for us.
Sounds to me like your department needs to start distributing its own perl distro.
Training our help desk to use CPAN really isn't part of the plan.
Why would your help desk need to know about CPAN, it's not like they're programmers?
I guess you haven't heard of PAR.
MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | ** The third rule of perl club is a statement of fact: pod is sexy. |
| [reply] [Watch: Dir/Any] |