Newsgroups: comp.lang.perl
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!convex!usenet
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Ruminations on the future of Perl
Message-ID: <1991Jun30.224532.23556@convex.com>
Sender: usenet@convex.com (news access account)
Nntp-Posting-Host: pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Software Development, Richardson, TX
References: <1991Jun28.212606.19054@convex.com> <RUSTY.91Jun28181513@groan.Berkeley.EDU> <trklf=c@rpi.edu>
Date: Sun, 30 Jun 1991 22:45:32 GMT
Lines: 20

From the keyboard of rodney@dali.ipl.rpi.edu (Rodney Peck II):
:In article <RUSTY.91Jun28181513@groan.Berkeley.EDU> rusty@groan.Berkeley.EDU (Rusty Wright) writes:
:>Similarly, in the "Syntax" section are examples for opening "foo" and
:>dying if it can't be opened, with the classic
:>
:>	open(foo) || die "Can't open $foo: $!";
:>
:>(but which I find to be just hackeritis show-off).
:
:I don't understand -- I use this all the time.  really.  what's the
:problem?

Perhaps those folks not heavily into shell programming do not take well 
to using && and || for flow control.  But those who are, do, and are 
glad it's there.

--tom
--
Tom Christiansen		tchrist@convex.com	convex!tchrist
		"So much mail, so little time."  
