From: "Magnus Lewis-Smith" <magnus DOT lewis-smith AT pace DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: DJGPP perl port vs ActivePerl line length
Date: Wed, 30 Aug 2000 10:54:09 +0100
Organization: Posted on a server owned by Pace Micro Technology plc
Lines: 30
Message-ID: <8oilke$ns4$1@nh.pace.co.uk>
NNTP-Posting-Host: dhcp-166-163.saltaire.pace.co.uk
X-Trace: nh.pace.co.uk 967629262 24452 136.170.166.163 (30 Aug 2000 09:54:22 GMT)
X-Complaints-To: newsmaster AT pace DOT co DOT uk
NNTP-Posting-Date: 30 Aug 2000 09:54:22 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I have a perl script which is used to automate CVS checkouts, the useful
fragment of which is:

while (<MODULES>) {
  s/\#.*//;
  next unless /\S/;
  if (/\A(\S+)\s+(\S+)\s*(\S+)?\s*\Z/) {
    my $command = "cvs -fQq -d $repos co -r $tag $1";
    print $command . "\n" if $verbose;
    system($command);
    die("$script: failed ($command)\n") if ($? >> 8);
  }
}

Under ActivePerl the script executes properly, but under the DJGPP port
lines longer than 127 characters get truncated, and $repos may often exceed
127 characters alone.  I am trying to encourage our department to move to
DJGPP entirely as our build environment, so I would prefer to use the DJGPP
perl if at all possible.

Is there a solution or workaround, or will I have to live with this and use
ActivePerl?

--
Magnus Lewis-Smith
magnus DOT lewis-smith AT pace DOT co DOT uk