[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: warnings ignoring parser configuration value
From: |
Patrice Dumas |
Subject: |
Re: warnings ignoring parser configuration value |
Date: |
Wed, 24 Feb 2021 00:03:54 +0100 |
On Sun, Feb 21, 2021 at 09:37:47AM +0000, Gavin Smith wrote:
> On Sun, Feb 21, 2021 at 12:40:40AM +0100, Patrice Dumas wrote:
> >
> > What about splitting %default_customization_values in two,
> > %default_parser_customization_values
> > and
> > %default_structure_customization_values
> > and put the options that are not rlevant for the parser in
> > %default_structure_customization_values
> > and modify tp/Texinfo/XS/parsetexi/Parsetexi.pm such that it does not
> > warn about keys in %default_structure_customization_values?
>
> That sounds sensible. It would make it easier to check that the
> customization variables for the parser were being handled.
> Maybe only the variables in %default_structure_customization_values
> could be set on the parser object.
I tried that too, but this was not possible with the current code, there
would be a need to add to the parsers something like set_conf(), instead
of having all the configuration options being set when initializing the
parser. I think that we can leave it like this, we could still revisit
later, but I am not convinced that it is needed.
--
Pat