Perl: differences between Win2k & Linux?

stoney79 · 01-13-2005, 05:12 AM

Hi there,

I've been having problems with a Perl script I've been given. It falls over at the following segment:

Code:

	open (PRJLISTFILE, "<$ENV{'_TMROOT'}/project/prjlist.txt");
	LOOP: while (defined($PrjListLine=<PRJLISTFILE>)){
		chomp $PrjListLine;
		print STDOUT "$PrjListLine\n";
		next LOOP if ($PrjListLine =~ /^\#/);
		next LOOP if ($PrjListLine =~ /^\s*$/);
		$PrjListLine =~ s/\#.*//g;
		$RootLocations = $RootLocations." ".$PrjListLine;
		print STDOUT "Current RL: [$RootLocations]\n"; 
	}
	print STDOUT $RootLocations;
	close PRJLISTFILE;

This should read a list of directory locations and create a list of them in the variable $RootLocations, each delimited by a space. This works fine on Windows, but under Linux it overwrites the first one each time, resulting in a rather munged variable. Any thoughts as to the difference?

I've checked and the textfile looks fine on both, so it's not a CRLF prob. All suggestions gratefully received!

Using ActiveState Perl v5.6.1 on both (originally using 5.8.1 in Linux, so have reverted back to 5.6.1)

Thanks,

Tony

rjlee · 01-13-2005, 08:25 AM

Do you mean that the file has a CRLF in both cases?

If so, then the Linux version will remove only the LF with chomp(), because Linux doesn't treat CR as a newline character.

This will also leave a CR at the end of each line, which the terminal will interpret as “go back to start of line”, hence why this would look the same on each line.

In this case, you could declare a local value for $/ to be CRLF to get around this problem, or (for instance) use a regexp to remove all whitespace (or all CRs and all LFs) from the end of the line.

stoney79 · 01-13-2005, 08:56 AM

Ah....

Yep - that's fixed it. I'm still a bit of a Linux newbie so haven't quite grasped the finer points of CR and LF! I thought it must have been that, but each time I loaded the file in an editor the customer ^Ms weren't there so I thought it wasn't that. But my friend showed me dos2unix and since then it's fixed! I've now hit another problem, but will investigate a bit more!

Thanks a lot rjlee!