You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the pim6sd .conf file parser requires a ; even though most settings end with a newline. To make editing the .conf a bit more "Made Easy" it would be preferable if the parser could also accept newline as a separator for configuration directives. Similar to mrouted, pimd, and smcroute. At least mrouted uses the same type of Yacc/Bison based parser (with the same ancestry).
This may seem like a complicated issue to start with, but the build system takes care of a lot of the problems with running yacc/bison and lex/flex. Most of the work is figuring out how the mrouted parser does it and porting that to pim6sd.
The text was updated successfully, but these errors were encountered:
Currently the pim6sd .conf file parser requires a
;
even though most settings end with a newline. To make editing the .conf a bit more "Made Easy" it would be preferable if the parser could also accept newline as a separator for configuration directives. Similar to mrouted, pimd, and smcroute. At least mrouted uses the same type of Yacc/Bison based parser (with the same ancestry).This may seem like a complicated issue to start with, but the build system takes care of a lot of the problems with running yacc/bison and lex/flex. Most of the work is figuring out how the mrouted parser does it and porting that to pim6sd.
The text was updated successfully, but these errors were encountered: