> sub callfritz{
> local STDIN < $InputData;
> local STDOUT > PREVIOUSLY_OPENED_HANDLE;
> eval `cat fritz.pl`;
> };
Unclear what you really mean there with the eval. But why not
simply allow
open(local *STDIN, "< $InputData");
open(local *STDOUT, ">&PREVIOUSLY_OPENED_HANDLE");
to do the obvious thing? You are very close to that now.
>is proposed as an alternative to doing the same thing
>with a variety of open2 calls.
That's unneeded even now.
>=head1 DESCRIPTION
>As an alternative to the Bourne shell style C<open> syntax
>described in `perldoc -f open`, this
That's a legacy term. I would avoid it.
>It will also provide another way to capture STDERR from
>within backticks.
And pray tell, what's so onerous about the status quo?
>Currently I do this kind of thing by using the
>file system as temporary storage.
I think you're doing that the hard way then. No need for such.
>another use of the angle brackets would be as a single-character
>print operator, similar to << in C++ streams.
EW!!!! No, no, no. Please don't do this. It is naughty to hide
I/O operations inside cutesy overloaded punctuation. Perl is already
too punctuation heavy. This helps nothing. It only makes it all
worse. If you want to use print, why make a short cut? Just use
print. We get so beaten up already over <FH> instead of readline(FH),
and now we're getting worse.
--tom
