Re: [PATCH 1/2] parse_options: Add flag to prevent errors for further processing

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jeff King <peff@...>
Cc: Shawn Bohrer <shawn.bohrer@...>, <git@...>, <madcoder@...>
Date: Wednesday, June 18, 2008 - 1:13 am

Jeff King <peff@peff.net> writes:


Not necessarily.  You could structure individual option parsers like how
diff option parsers are done.  You iterate over argv[], feed diff option
parser the current index into argv[] and ask if it is an option diff
understands, have diff eat the option (and possibly its parameter) to
advance the index, or allow diff option to say "I do not understand this",
and then handle it yourself or hand it to other parsers.


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC] convert shortlog to use parse_options, Shawn Bohrer, (Tue Jun 17, 11:03 pm)
Re: [PATCH 1/2] parse_options: Add flag to prevent errors fo..., Junio C Hamano, (Wed Jun 18, 1:13 am)
Re: [PATCH 1/2] parse_options: Add flag to prevent errors fo..., Johannes Schindelin, (Wed Jun 18, 12:50 pm)
Re: [PATCH 1/2] parse_options: Add flag to prevent errors fo..., Johannes Schindelin, (Sun Jun 22, 3:07 pm)
Re: [PATCH 1/2] parse_options: Add flag to prevent errors fo..., Johannes Schindelin, (Mon Jun 23, 4:24 pm)
[PATCH 2/2] git shortlog: Modify to use parse_options, Shawn Bohrer, (Tue Jun 17, 11:03 pm)