[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-porters
Subject:    Re: [PATCH] docs more open() and $_ related entries
From:       "Joshua ben Jore" <twists () gmail ! com>
Date:       2008-01-08 22:32:12
Message-ID: dc5c751d0801081432v5eafce22g2f70f75d4246e41f () mail ! gmail ! com
[Download RAW message or body]

On Dec 26, 2007 9:44 PM, Michael G Schwern <schwern@pobox.com> wrote:
> Aristotle Pagaltzis wrote:
> >> I don't see the benefit to the reader.
> >
> > It has nothing to do with readability and everything to do with
> > robustness and safety. You're arguing something that to me feels
> > dangerously close to "I don't see the benefit to the the reader
> > of using placeholders in SQL and they're overkill in simple
> > cases."
>
> I've never considered the filename part of open() as a hole before, not
> syntactically anyway.  Are you thinking like:
>
> $user_input = '>important_file';
> open my $fh, $user_input;

My /mnt/squeak/classes/Integer/Instance methods directory contains the
following files:

<.st
<<.st
>.st
>>.st

If someone were lulled into complacency by seeing two-argument open in
the perl document they'd blow up when attempting to read my SmallTalk
files. I don't want Perl coders taught to use things that break like
two-argument open.

Josh
[prev in list] [next in list] [prev in thread] [next in thread]