Re: Why do here-docs have to end with a newline, not EOF?

I'm using perl 5.8.8 version for testing your little snippet and it works well. I've executed it with and without the final LF; in unix and in MSDOS format (with CR-LF); and the snippet still works well ...

perl -Te 'print map { chr((ord)-((10,20,2,7)[$i++])) } split //,"turo"'

Comment on Re: Why do here-docs have to end with a newline, not EOF? Download Code

Replies are listed 'Best First'.
Re^2: Why do here-docs have to end with a newline, not EOF? by ikegami (Patriarch) on May 12, 2008 at 01:05 UTC
Really? I can reproduce the OP's results on WinXP and Linux. WinXP, Perl 5.8.8, ActivePerl 820 `>perl -e"print qq{print <<ENDHERE\nabc\nENDHERE}" > test.pl >perl test.pl Can't find string terminator "ENDHERE" anywhere before EOF at test.pl +line 1. >perl -e"print qq{print <<ENDHERE\nabc\nENDHERE\n}" > test.pl >perl test.pl abc >` [download] Linux, Perl 5.8.4 `$ perl -e'print qq{print <<ENDHERE\nabc\nENDHERE}' > test.pl $ perl test.pl Can't find string terminator "ENDHERE" anywhere before EOF at test.pl +line 1. $ perl -e'print qq{print <<ENDHERE\nabc\nENDHERE\n}' > test.pl $ perl test.pl abc $` [download] If I were to guess, I'd say the parser looks for <"\nENDHERE\n"> instead of <"\nENDHERE" followed by either "\n" or end of file>, and it does so because it's easier and because every line is suppose to end with a line feed in unix.	[reply] [d/l] [select]
Re^3: Why do here-docs have to end with a newline, not EOF? by turo (Friar) on May 12, 2008 at 01:18 UTC
yeep ... my editor was adding the final '0a' in the file without consulting me :-S ... `perl -Te 'print map { chr((ord)-((10,20,2,7)[$i++])) } split //,"turo"'`	[reply] [d/l]


Pathologically Eclectic Rubbish Lister
	PerlMonks