Quote:
>: #!/usr/local/bin/perl
>: close STDIN;
>: $expn = </hp*>;
>: __END__
>:
>: In looking at trace output (for s300, maybe different than s700), I
>: noticed that csh appears to make some assumptions about file
>: descriptors 0, 1, and 2. Since 0 (STDIN) has been closed, it will be
>: used again for the next open file. Perhaps this confuses someone
>: (perl or csh)?
>Many standard Unix utilities will get confused if you hand them closed
>fds 0, 1, or 2. It's considered vaguely antisocial to do so. The
>usual workaround is to open /dev/null instead of closing.
>: I don't know exactly what is going on here, but it seems to me that
>: it is time for perl to do its own globbing.
>It's time for Perl to do a lot of things. Unfortunately, I can only
>work on one of them at once, max. If I were going to work on it, I'd
>probably take a globbing Perl module and stitch it in to get called
>transparently by <*>. In this sense, Perl should *not* do its own
>globbing, but should rely on (potentially architecture dependent)
>modules to do so. We already did something similar with the
>implementation of dbmopen.
Umm, a quick peek at the Perl 5 Module List shows:
=======================================================================
File Names, File Systems, File Locking and File Handles
Name DSLI Description Info
----------- ---- -------------------------------------------- -----
File::
::KGlob cdcf Filename globing (ksh style) TYEMQ
=======================================================================
Information / Contact Reference Details (in alphabetical order)
Ref Contact Details
----- ------------------------------------------------------
From memory Perl 5 has a 'glob' function which the File::KGlob module
can override if desired. Sadly, in Perl5.000, the <*> shorthand does
not use the glob function and hence can not be overridden by the
File::KGlob module.
That may change in Perl5.00x. I don't know if Larry regards it as a bug.
Quote:
Regards,
Tim Bunce.