Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal L. Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: print <FILE>;
Message-ID: <1991Apr8.164630.2388@iwarp.intel.com>
Date: 8 Apr 91 16:46:30 GMT
References: <1268@sicsun.epfl.ch> <$dG&j&j1@cs.psu.edu>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal L. Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 15
In-Reply-To: flee@cs.psu.edu (Felix Lee)

In article <$dG&j&j1@cs.psu.edu>, flee@cs (Felix Lee) writes:
| Does anyone have a complete list of places where scalar and array
| contexts are forced?

Page 378 of The Book begins "Appendix A: the Semi-Formal Description",
from which a complete list of scalar and array contexts may be
derived.  That is, if someone has the time... I'm busy finishing up
chat.pl :-).

%_ = ("Just another Perl hacker,",0); print keys _;
-- 
/=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'..."====/