Re: close ARGV inside a while

jesuashok, your recent posts seem to mostly consist of code snippets that are suspiciously impractical, followed by the question "please explain".

I don't mind that much, but please try to be more clear about why you think the output is strange. At the very least, try to provide an example of what you think the output should be.

If you don't do that we end up going round and round and in the end still won't know what's going wrong for you.

I'm not even going to attempt to answer your post here until you explain what you think is wrong with the output, since it seems too obvious to me why it does what it does.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re: close ARGV inside a while

Replies are listed 'Best First'.
Re^2: close ARGV inside a while by Fletch (Bishop) on Jun 08, 2006 at 14:17 UTC
Can't you see? You close the filehandle and it mysteriously doesn't return any more lines and the `<>` operator returns an undefined value? That's just what The Man wants you to believe. The Truth Is Out there. I mean, come on! Maybe you need a refresher course. And why would a Wookie live on Endor? That does not make sense! Wait . . . now I'm confused. Where does the pony come in?	[reply] [d/l]
Re^2: close ARGV inside a while by jpeg (Chaplain) on Jun 08, 2006 at 18:14 UTC
I wouldn't presume to know (or ask for an explanation) as to what Jesusahok is doing, but this node may explain what he's up to. I've seen obviously broken code in perldoc with explanations of why they don't work. I don't think these questions are unreasonable in that context. -- jpg	[reply]
Re^3: close ARGV inside a while by Fletch (Bishop) on Jun 08, 2006 at 18:54 UTC
So he's got new people . . . and he's trying to find exercises for them to do to help them learn . . . so he's asking people on Perlmonks about broken example code . . . so that these people he's trying to bring up to speed . . . can learn . . . Wait, I think the Wookie just ran off with the pony there. I could see the benefit in using intentionally broked code as a teaching tool; however if the teacher themselves doesn't understand why it's broked they're probably not the best candidate to be teaching people (at least not with their present level of knowledge; the optically unreceptive pathfinding the optically unreceptive as it were). Addendum: I will grant that Increment avoids warning unexpectedly is somewhat wonky behavior, and whlle I can deduce why it behaves that way I certainly could see how it's surprising. However calling things like Data::Dumper converting characters to their backwhacked double quote equivalent when you explicitly tell it to do so or expecting to get data from closed filehandles "unexpected" behavior just makes me want to quote Inigo: "You keep using that word. I do not think it means what you think it means.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.


laziness, impatience, and hubris
	PerlMonks