Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re: Re: Parsing your script's command line

by xphase_work (Pilgrim)
on Jun 14, 2001 at 18:38 UTC ( #88433=note: print w/replies, xml ) Need Help??

in reply to Re: Parsing your script's command line
in thread Parsing your script's command line

That statement only applies to GNU/Linux systems, or at least systems that use the GNU Binutils. Most commercial UNIX vendors don't have long option support in their Binutils. Sun and HP's versions of tar don't support long arguments, but FreeBSD and Linux support both forms of arguments.

While the choice of which arguments your programs accept is your choice, many people choose to follow the standard their OS vendor uses. I think that the table showing only the short arguments is good because short arguments is more of a standard then GNU-Style arguments, but I think that including a link to GNU Coding Standards Option Table, with an explaination that these are used mainly on GNU/Linux or GNU Binutils systems would be useful.


  • Comment on Re: Re: Parsing your script's command line

Replies are listed 'Best First'.
Re: Re: Re: Parsing your script's command line
by mugwumpjism (Hermit) on Jun 14, 2001 at 23:20 UTC

    Ah, but this is Perl, you're supposed to be thinking cross platform. And what is more cross platform than GNU?

    I'd recommend looking at the table, and using what's on there unless you have a good reason not to.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2020-09-19 02:16 GMT
Find Nodes?
    Voting Booth?
    If at first I donít succeed, I Ö

    Results (114 votes). Check out past polls.