Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!cadence!acae037!eversole
From: eversole@acae037.cadence.com (Richard Eversole; x6239)
Newsgroups: comp.lang.perl
Subject: file handle anomaly
Message-ID: <1991Jun27.180332.6471@cadence.com>
Date: 27 Jun 91 18:03:32 GMT
Sender: usenet@cadence.com (USENET News)
Reply-To: eversole@acae037.cadence.com (Richard Eversole; x6239)
Organization: Cadence Design Systems, Inc.
Lines: 41

#!/util/bin/perl
#  ^-----------^---- replace with your favorite perl path
#
#  This script shows an interesting anomaly of perl
#
#  Could some one please explain why this happens and
#  why the last print is a parse error.
#
#  I kind of understand that perl is not able to determine
#  that $ofile is a file handle in the last example.
#
#  My question is: Shouldn't perl be able to correctly parse
#                   this ?
#
#  $Header: perl.c,v 4.0 91/03/20 01:37:44 lwall Locked $
#  Patch level: 0
#

$ofile = STDOUT ;

print $ofile '',<<EOD ;
This works
EOD

print STDOUT <<EOD;
This works
EOD

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

-- 
  
  =====================================================================

    eversole@cadence.com
  
    Live long and prosper !