On Wed, Aug 7, 2013 at 11:28 AM, Mark Morgan Lloyd <[email protected]> wrote: > I think there are some options which could be usefully filtered out, at the > very least -?.
Oops, the filtering out code was broken. Now it works again in r42367. > I imagine it's going to be "fun" reconciling any options modified on the > "All Options" form with the existing "Config and Target" > http://bugs.freepascal.org/view.php?id=20311 > http://bugs.freepascal.org/view.php?id=20310 etc. I am not sure if we want that. The idea of parsing the fpc's help output is to support all available options, including the future ones added by fpc developers. It does not make sense to analyze their meaning much. Important options must have their own dedicated and intelligent GUIs. The bugs you listed must be fixed obviously. If someone sets the same option using both a dedicated GUI and the all options GUI, no problem, the compiler accepts it. I improved the parser so that -Oo, -OW and -Ow options are selectable individually instead of a drop-down list. Only the quoted strings must be handled better, otherwise the parser is OK. The GUI may be changed to a grid but that is another thing. Dimitry is working on a competing solution with self made JSON config files. They are easier to parse but they must be maintained for every fpc version and architechture. Forgetting the maintenance undermines the whole idea. IMO the right place for such info is the fpc project itself. Juha -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
