Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!relay.nswc.navy.mil!oasys!mimsy!mojo.eng.umd.edu!stripes From: stripes@eng.umd.edu (Joshua Osborne) Newsgroups: comp.lang.perl Subject: Re: Ruminations on the future of Perl Message-ID: <1991Jul01.034333.27191@eng.umd.edu> Date: 1 Jul 91 03:43:33 GMT References: <1991Jun30.224532.23556@convex.com> Organization: College of Engineering, Maryversity of Uniland, College Park Lines: 32 In article <1991Jun30.224532.23556@convex.com> tchrist@convex.COM (Tom Christiansen) writes: >From the keyboard of rodney@dali.ipl.rpi.edu (Rodney Peck II): >:In article 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. Lots of people have assumed he is objecting to the use of || for flow control. However I think he is objecting to open(foo) using $foo to find the file-name to open. It is certinly a less then oft-used feature. I almost never use it. I don't rember any example programs using it. However I don't rember any JAPH's using it, so it can't be ther just to make obscure perl code :-) (this is what I assumed he was refering to when I made my orig reply) -- stripes@eng.umd.edu "Security for Unix is like Josh_Osborne@Real_World,The Multitasking for MS-DOS" "The dyslexic porgramer" - Kevin Lockwood "CNN is the only nuclear capable news network..." - lbruck@eng.umd.edu (Lewis Bruck)