Proposed lexer for parsing krb5.conf files

[Sam Hartman]

>>>>> "Paul" == Paul Moore <paul.moore at centrify.com> writes:

    Paul> Why not go crazy and drag krb5 kicking and screaming into
    Paul> the 21st century and make the config file XML You get the
    Paul> parser, editors, validation, low level API, pretty display,
    Paul> base syntax rules, base extension capability all for free

Because it would complicate the code significantly and it would lose
us compatibility with existing files.

I think the build headaches for dealing with xml toolchains would be
worse than implementing Joe's lexer.