9 Jun
2009
9 Jun
'09
6:16 a.m.
Vladimir Prus skrev:
Thorsten Ottosen wrote:
This seems wierd. Why would I want a vector of values, yet only parse one of the trailing argument? multitoken options are evil, because of parsing ambiguities. The motivating examples for vector<string> option is the -I option of a compiler -- where each instance of -I takes a single path -- and which seem to work just fine. I fail to see this evilness. Something like
foo.exe --new_edge 1 --new_edge 2
is hardly readable. How can there be difficulties in parsing everything until the next --arg is reached?
Given
--new_edge 1 -2
Is -2 a short option, or part of --new_edge?
I specified vector<unsigned>, so it can't be a value in the list. -Thorsten