open gives examples of how to save, redirect, and restore file handles. That example does not do things the way you did. Yes, doing it the wrong way is why your code isn't redirecting correctly. Yes, that was the question you asked that I was addressing. No, I had no comment on your second question.
The open examples (implicitly) pass typeglobs as arguments to open(). They don't use any typeglob syntax, not a single use of * except in some example regular expressions). They don't manipulate typeglobs directly in hopes of having a similar impact on the file handles contained in them.
Rephrased more clearly and more correctly: Don't copy, save, or restore typeglobs that contain open file handles.
And, of course, when the standard documentation shows how to do something, it is often a good idea to pay attention.
I am not introducing new typeglobs (other than a localised version of STDERR)
Yep, you even figured out which one I'm talking about, but refused to belive it? :)
If it was a good idea to save/restore a file handle with a simple local(*STDERR), do you think the example of how to save/restore a file handle in the standard open docs would have avoided such?
- tye
In reply to Re^3: diagnostics, STDERR, and codepage conversions (open)
by tye
in thread diagnostics, STDERR, and codepage conversions
by Tanktalus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |