Juha Manninen wrote:
One more thing:
FPC could give much better and consistent info about the options than
what the current "fpc -i" and "fpc -h" do.
For example the help refers to "fpc -i" for possible values for
selection lists but does not mention which list to look for. I had to
make a hard-coded mapping which again undermines the idea of a generic
parser.
Also, -Oo, -OW and -Ow options must be hard-coded to show individual options.
Can somebody please verify that my guesses were right. I hope in
future fpc help will be more exact and consistent. It would benefit
not only my parser but also human readers.
Would there be any mileage in having the compiler output this sort of
thing in XML or some similar formal markup?
What happens if the compiler emits any language other than English?
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
