Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!iWarp.intel.com!news
From: merlyn@iWarp.intel.com (Randal L. Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: file handle anomaly
Message-ID: <1991Jun27.224647.2971@iWarp.intel.com>
Date: 27 Jun 91 22:46:47 GMT
References: <1991Jun27.180332.6471@cadence.com>
Sender: news@iWarp.intel.com
Reply-To: merlyn@iWarp.intel.com (Randal L. Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 38
In-Reply-To: eversole@acae037.cadence.com (Richard Eversole; x6239)
Nntp-Posting-Host: se.iwarp.intel.com

In article <1991Jun27.180332.6471@cadence.com>, eversole@acae037 (Richard Eversole; x6239) writes:
| print $ofile <<EOD;
| This returns the parse error
| parse error in file bug.pl at line 30, next 2 tokens "This returns"
| Execution of bug.pl aborted due to compilation errors.
| EOD

Ugh.  Consider the difference between:

	print $ofile <<EOD;
	print <<EOD;
	EOD

and

	print $ofile <<3;
	print <<EOD;
	EOD

You cannot know that the $ofile is a handle until you have seen the 3.
That's too far for the one-token-ahead parser to go.  It presumes you
mean left-shift in this case.  Try this as a workaround:

	print $ofile (<<EOD);
	print <<EOD;
	EOD

Pages 86 and 87 of the First Edition of The Book give the entire chart
of context-sensitive operators and a description of the pitfalls.

(Note the words "First Edition".... hmmm.... :-)

print "Just another Perl hacker," x (1024 >> 10)
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Intel: putting the 'backward' in 'backward compatible'..."====/