Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: Re: RFC: new module r (or R)

by etcshadow (Priest)
on Mar 05, 2004 at 19:25 UTC ( #334332=note: print w/ replies, xml ) Need Help??


in reply to Re: RFC: new module r (or R)
in thread RFC: new module r (or R)

Interference with GetOpt* is a good point... Obviously, the only way such a collision could occur is if there were a directory named "--whatever" or "-w", etc. But it's still the sort of thing that shouldn't be allowed to interfere.

More reason, I think, to go with the -MR-type notation... as that would give more control (over when and where) to someone who was writing a script, or other module, but wanted to incorporate the @ARGV-recursion of this module.

Of course, another route would be to make it all under something like RecursiveARGV.pm, and provide a stub r.pm that was just:

use RecursiveARGV;
Making perl -mr exactly the same as perl -MRecursiveARGV, but allowing people to do more fun stuff in their scripts like:
#!/usr/bin/perl require RecursiveARGV; # cleans @ARGV of any switches here, # leaving only files GetOpt(...); # now @ARGV becomes directory-magic RecursiveARGV->import();

Update: I changed midstream between referring to a more full-fledged module as R.pm and RecursiveARGV.pm... and things got a little tangled up.

------------ :Wq Not an editor command: Wq


Comment on Re: Re: RFC: new module r (or R)
Select or Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://334332]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (14)
As of 2015-07-06 12:49 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (74 votes), past polls