[Xorp-hackers] Config Var <-> Config mode

[Kristian Larsson]

How about removing ":" from the configuration file
and simply ignoring ";" at the end of line. This
would allow cut and paste with minimal changes.
Plus it would be more JunOS like.

One of the thing that networking people really
love about Juniper is it's CLI, and thus making
XORP very similar to it is clever. However there
are several points where XORP differ from JunOS, IMHO
this is often not to the better. The subject brought
up here is one of them.
Another is that of the "set" command which in XORP
is split into create and set. Makes sense
programming wise, not user wise. I know I have
brought this up before:
JunOS:
set prefix-list test 1.0.0.0/24
set prefix-list test 2.0.0.0/24
results in 
prefix-list test {
  1.0.0.0/24;
  2.0.0.0/24;
}

XORP:
create network4-list test elements 1.0.0.0/24,2.0.0.0/24
results in
network4-list {
  elements: "1.0.0.0/24,1.0.1.0/24"
}

Which one is the easier one to scim through? Which
one is easier to add prefixes to?

I can't see anything other than programming
benefits to XORPs way.

Am I the only one of this opinion?

   Kristian.

On Wed, Nov 02, 2005 at 07:57:50PM +0100, Patrick Preuss wrote:
> Hello
> 
> I have seen following if you configure a single line variable you write
> varname value<cr> and you get varname: value or varname: "value". I think
> this should be varname value; where the cli parser accepts both, varname
> value<cr> and varname value;<cr>, I think this is what Juniper does.
> 
> Currently you cannot cut and past the config;-( 
> 
> Additionally the behavior of bool values should be in the way:
> Varname; means the variable is true 
> And if you delete it the value is false. 
> 
> Gruss 
>    Patrick Marc Preuss 
>    Nordstrasse 28
> 41569 Rommerskirchen
>  
>    
> 
> 
> 
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers@icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers