Re: [PATCH 2/2 nft] scanner: fix parsing of tc handle

[Patrick McHardy <kaber@trash.net>]

On Thu, Feb 13, 2014 at 11:51:12AM +0000, Patrick McHardy wrote:
> On Thu, Feb 13, 2014 at 12:41:12PM +0100, Pablo Neira Ayuso wrote:
> > hexstring:hexstring
> > hexstring:
> > :hexstring
> > ---
> > The spaces to separate the key and the action in dictionaries is very
> > important, otherwise (with this patch) the scanner misinterprets this.
> > 
> >  # nft add filter input tcp dport vmap { 25:drop }
> >  <cmdline>:1:41-43: Error: syntax error, unexpected string, expecting comma or '}'
> >  add rule filter input tcp dport vmap { 25:drop }
> >                                         ^^^
> > I think we can just document this, I don't see any better solution for this
> > at this moment.
> 
> Let me try if I can come up with something ...

I think we might be able to do something with flex "trailing contexts",
though I didn't manage to figure it out yet.

Generally it seems like using a ':' in maps might not be the best idea
after all, its used for too many other things already. This might be
the reason why I initially used =>, not sure anymore.

Is there a reasonable alternative to ':' with a single character?