Yes, I am aware of Term::ANSIColor, but I don't use it for two reasons - firstly, the module is not available, and secondly, I want to iterate through the possibilities and show up the terminal deficiencies. Fixing problems with color use is not always easy, and having those escape sequences helps me.
pbeckingham - typist, perishable vertebrate.
| [reply] |
Fair enough, even though I can never fathom why people mention “it’s not installed” for pure-Perl modules.
Makeshifts last the longest.
| [reply] |
Oh, I can help you there. I write Perl code for a living, and that code operates in two different environments. In a Company-internal environment, I use Perl 5.8.5, and all the modules I want. I use a variety of modules, and would generally prefer to use a module than write the code myself, provided said module isn't junk. I imagine you have similar experiences, but that's not my point.
The problem lies in the other environment - a highly controlled production environment, servicing tens of millions of customers. I cannot simply place new modules in that environment - I have to get all the code certified before release. Even harder than getting a module out there, is updating Perl itself, as that would necessarily trigger a full-scale regression of all existing deployed code, not to mention the re-certification of Perl itself. No one has that kind of budget, and so I necessarily work with an old version of Perl, and a limited set of modules. There are further restrictions, but I won't go into those.
Our production environments have a tendency to operate on the "if it ain't broke" mentality, and even though I don't like it, I understand it.
pbeckingham - typist, perishable vertebrate.
| [reply] |
Not everyone has permissions to install CPAN modules on the machine they're working on.
| [reply] |
