netdev
[Top] [All Lists]

Re: netlink tester program

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: Re: netlink tester program
From: David Brownell <david-b@xxxxxxxxxxx>
Date: Mon, 02 Jun 2003 18:56:23 -0700
Cc: rddunlap@xxxxxxxx, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
References: <32804.4.64.196.31.1054351332.squirrel@www.osdl.org> <20030530.234211.102567405.davem@redhat.com> <20030602140452.039248de.rddunlap@osdl.org> <20030602.145619.71112623.davem@redhat.com>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
David S. Miller wrote:
   From: "Randy.Dunlap" <rddunlap@xxxxxxxx>
   Date: Mon, 2 Jun 2003 14:04:52 -0700

   Does anyone have documentation (or semantics) for rtnl_talk()?
   or just some blurb about it?

I always have to wonder about someone who can't live with just
working code to study, and absolutely requires some document
describing it.

What is better or more accurate description than code itself!?!?!

Well, the difference between code and its spec is generally a bug that needs to be fixed ... which can be in the code as well as in the spec. And for reasonable design specs, it's more likely in the code.

But if there's only the code, it gets a lot more
troublesome when things don't behave "as expected".

People who are in a position to change the code
to meet their expectations may not care, but that's
rarely a significant chunk of the user community.

And in particular, writing tests against the code
is generally the wrong way to go.  They need to be
written against some kind of spec.

- Dave




<Prev in Thread] Current Thread [Next in Thread>