$include_dir="/home/hyper-archives/boost-users/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Ovanes Markarian: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Previous message: Robert Ramey: "Re: [Boost-users] Compiler warnings from Macs, IBM acc, Borland, Comeau, Metroworks, et al - are they a Problem?"
- Next in thread: Ovanes Markarian: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Reply: Ovanes Markarian: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Reply: Vladimir Prus: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Reply: Mika Heiskanen: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
I am studying Boost Program Options library and I am curious, why was it
choosen double dashes as the token to identify an option in the command line
?
Example:
my_program --help
Would not a single dash be enough and less verbose ?
What is the rationale behind that ?
Thanks,
--
Mauricio Gomes
"Think globally, act locally".
- Next message: Ovanes Markarian: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Previous message: Robert Ramey: "Re: [Boost-users] Compiler warnings from Macs, IBM acc, Borland, Comeau, Metroworks, et al - are they a Problem?"
- Next in thread: Ovanes Markarian: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Reply: Ovanes Markarian: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Reply: Vladimir Prus: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
- Reply: Mika Heiskanen: "Re: [Boost-users] Boost Program Options: Just curiosity, why double dashes ?"
$include_dir="/home/hyper-archives/boost-users/include";
include("$include_dir/msg-footer.inc");
?>