Oliver Schroeder wrote: > Hi List. > > I think that our command line processing is way to scattered and thus > error-prone. Don't feel affronted, I just decided for myself to never touch > anything related to commandline processing in flightgear. > > Would it help to have a generic central commandline-parser, which forces > developers to provide a description?
Perhaps you should provide us a definition for a generic central commandline-parser, because I always thought it was already the case ( I am biased, I wrote this code ). Options are described in a single array of structures and the processing is very simple and generic. Have a look at options.cxx. Maybe it can be improved, by providing descriptions for instance, but the step was made years ago to avoid to have huge switch or if/elseif/else constructs that compilers could not compile. -Fred ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
