Re: comments on version 2 of protocol draft

[Bobby Krupczak <rdk@krupczak.org>]

Hi!

> >I agree with this. Does anyone on the list have a problem with 
> >removing the default parameter values?
> 
> not really, but in the cases where it is obvious that one value
> will be used much more than the others, defaults make things
> easier on the application programmer.

I dont agree per se probably because I do not really understand what
you mean by "easier on the application programmer".

In general, most APIs will have arguments.  Defaults often take the
form of passing null value.  In this case, passing "value" instead of
"NULL" seems to be no easier or worse.  Not having defaults does,
however, make the code "easier" for the application programmer to
read.

Bobby

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>