[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r8621 - in branches/1.0.x: . tools/hook-scripts

From: Juanma Barranquero <jmbarranquero_at_wke.es>
Date: 2004-02-16 16:11:28 CET

On Mon, 16 Feb 2004 09:24:03 -0500
John Peacock <jpeacock@rowman.com> wrote:

> This may be the _only_ additional release on the 5.005xx maint branch. There
> are a few lost souls whose IS department refuses to support newer Perl's, and if
> hint files and other compiler fixes can be backported, that is a good thing.

There are quite a lot more than a few souls. I work in what could be
considered a Perl shop; we publish legal stuff, both printed media and
CD/DVD, and several critical steps in our production processes are done
in Perl (mostly to enter data into our DB, but not just that). When our
system was implemented, 5.005 was current, and it's not been touched
since (why risk?). If someone seriously proposed to our tech bosses to
switch to a newer Perl, there'd be heart strokes all along the building.

In a previous life, around 1989~90, I did some Perl programming for an
import/export bookshop. To this day, their daily workflow depends on
those scripts, which must be, what? 5.003 or 5.004? I wouldn't dream of
making them switch, either...


> There are plenty of reasons to 'require 5.6.1' or even better in new code. '^W'
> and 'use warnings' is only one of them...

...I think you missed this bit from my message:

> This is not an opinion about the $^W vs "use warnings" issue, just an
> aside comment.

so I'm not really advocating to be back-compatible with 5.005; heck, I
have 5.8.2 on machines I administer, and quite happily, too. I just
commented on the "hardly anyone still supports 5.005" bit.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 16 16:11:56 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.