Skip to content

parser: accept non-words as first tokens & numbers as word tokens#6

Merged
donaldsharp merged 2 commits intoFRRouting:masterfrom
opensourcerouting:dev/osr/vty_pending
Dec 16, 2016
Merged

parser: accept non-words as first tokens & numbers as word tokens#6
donaldsharp merged 2 commits intoFRRouting:masterfrom
opensourcerouting:dev/osr/vty_pending

Conversation

@eqvinox
Copy link
Copy Markdown
Contributor

@eqvinox eqvinox commented Dec 16, 2016

No description provided.

There seems to be no reason why numbers don't work as plain word tokens;
this is useful to have "number choices" or constants, e.g. <128|192|256>
for bit encryption lengths.

Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
This removes an artificial restriction for the first token in a
command's graph to be a WORD_TKN.  The intention seems to be to prohibit
empty paths through a command, and to restrict "explosion" of choices in
the root node.

The better approach to the former is to check for an empty path after
the definition is parsed.  The latter will happen anyway, by duplication
of the command, which just makes it worse...

Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
@donaldsharp
Copy link
Copy Markdown
Member

Thanks all!

@donaldsharp donaldsharp merged commit 6cc1ba0 into FRRouting:master Dec 16, 2016
@eqvinox eqvinox deleted the dev/osr/vty_pending branch January 19, 2017 13:04
eqvinox referenced this pull request in opensourcerouting/frr Mar 25, 2017
Build Quagga without SSH support of RTRlib
@louberger louberger mentioned this pull request Dec 13, 2017
@rwestphal rwestphal mentioned this pull request Jul 9, 2018
cfra referenced this pull request in opensourcerouting/frr Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants