Re^3: Perl fIle handles

in reply to Re^2: Perl fIle handles
in thread Perl fIle handles

No, actually I just wanted to demonstrate that he could include the my within the open statement, but I can see how you could think I was implying something else. It was up to him to simply read the docs for open to see how to use the three parameter form.

Also, I'd advise against ever using the three parameter form of open when wanting read mode. It's much better to just let read mode be assumed so you don't risk putting the symbol in the wrong direction and overwriting your file.

Just my .02

Comment on Re^3: Perl fIle handles

Replies are listed 'Best First'.
Re^4: Perl fIle handles by lidden (Curate) on Jun 16, 2011 at 06:21 UTC
Also, I'd advise against ever using the three parameter form of open when wanting read mode. It's much better to just let read mode be assumed so you don't risk putting the symbol in the wrong direction and overwriting your file. And risk having the second arg contain something scary? `$file = '> somefile';`	[reply] [d/l]
Re^5: Perl fIle handles by wind (Priest) on Jun 16, 2011 at 22:17 UTC
That's a fair point, although I'm not sure I would qualify that as "scary". Given most of the file operations I perform are ones where I'm specifying the filename passed in the variable, I don't see this as a big risk. However, if there was ever a point where the file was specified in by the user and not validated in any way, then doing the three parameter form of read mode would be wise. For me at least, the right of being lazy is going to win out for this small risk otherwise. I find mistyping to be a bigger worry then intentional mischief.	[reply]

In Section Seekers of Perl Wisdom