Front page | perl.perl5.porters |
Postings from February 2014
On Thu, Feb 20, 2014 at 12:22 PM, <CARROS1@nationwide.com> wrote:
>
> So this means it doesn't mater if you have a user base doing production work
> with it and what processes will potentially break.
> Soon as this is not supported many shops will have no choice but to rewrite
> stuff to remove perl from our systems.
> Lack of support in the main stream pretty much mean end of life of the
> product.
>
> I have no idea what your actually needing. I have access to a system but
> can I promise it will always be available
> only if I could promise I'll always have the same position which in IT isn't
> always gold
>
> Sandra
>
Well then you can make a business case for helping us maintain
EBCDIC in core.
So you can say something like the following to your boss:
Either we dedicate some time on a recurring basis on one of our machines
for testing Perl, or we will have to spend a lot of time moving to
a new language.
If you aren't upgrading your Perl binaries, then you can still continue
to use the version(s) you have already. You just won't be able to use the new
features and performance enhancements that are being added to Perl every year.
Really all that is being asked is that someone compile Perl, and run some tests
on a regular basis. Which can, and should be automated.
With the promise to continue to do so for the foreseeable future.
If you think you can get this to happen, I'm sure that there are plenty
of people who would be willing to help you set things up.
Thread Previous
|
Thread Next