Re-designing the config parsers

Marcin Siodelski marcin at
Fri Sep 12 13:44:16 UTC 2014

On 12/09/14 12:44, Francis Dupont wrote:
> Tomek Mrugalski writes:
>> On 11.09.2014 18:01, Francis Dupont wrote:
>>> Marcin Siodelski writes:
>>>> I should also explain that we discussed with Tomek a use of Bison
>>>> framework ( in Kea.
>>> => I heavily used bison (and other LALR(1) parsers) in the past...
>>> BTW if you want to provide a parser style config, IMHO the best
>>> available is JunOS from Juniper (far better than the Cisco config).
>> No, we don't want to change the format. It will stay as it is.
>> The plan is to refactor/redo the code that parses that input.
> => so you have bison and equivalent, and for hand written parsers
> top down vs bottom up.

So, a statetement about bottom-up vs top-down doesn't tell me much if I
can make Bison parse the elements of the configuration in a desired
order. So for example, the simplified configuration file:

dhcp-option-fqdn = ""
dhcp-option-fqdn has type FQDN

defines a value for the new option called "dhcp-option-fqdn" in the
first line and the option format in the second line.

So, I want the parser to read the format of the option (second line)
before reading the option data "" and I want to report a
parser error if the "" is not a legal fqdn.

Is this configurable?


More information about the kea-dev mailing list