Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!convex!news
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.lang.perl
Subject: Re: the version problem
Message-ID: <1991Feb12.202147.1411@convex.com>
Date: 12 Feb 91 20:21:47 GMT
References: <20326:Feb1103:33:0491@kramden.acf.nyu.edu> <1991Feb11.204619.16651@convex.com> <498:Feb1204:50:5691@kramden.acf.nyu.edu>
Sender: news@convex.com (news access account)
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Software Development, Richardson, TX
Lines: 24
Nntp-Posting-Host: pixel.convex.com

From the keyboard of brnstnd@kramden.acf.nyu.edu (Dan Bernstein):
:> Dan, you seem to want more -- do you think an analysis
:> program as I mentioned above would suit you, even if it didn't test
:> for bug conditions since fixed?
:
:It would certainly help.

I've been poking at the problem, and for now it look like Laziness is
going to win out over Impatience: I'm just going to use the version-
checking wrapper I first posted.  Making a program that wraps this
stuff around a script that I send out is the easiest way.

I will amend the message to read:

    Attempting to continue anyway; wrong answers, coredumps, or syntax 
    errors may result.

As I found various things that coredump in PL18 scripts that are
just fine in the PL44 ones.  I'm hoping that 4.000 will serve as
a reasonable baseline release and ameliorate the problem somewhat.

--tom
--
 "All things are possible, but not all expedient."  (in life, UNIX, and perl)