use API setter routines instead of accessing struct iperf_test directly

[GoogleCodeExporter]

We've run into a few bugs now in the general category of code accessing members 
of struct iperf_test directly instead of using the API's setter routines.  Some 
of the setter routines have additional semantics besides just setting the 
value, and direct access skips that.

It might be nice to spend a little time moving some routines into files which 
include iperf_api.h but not iperf.h, so that the compiler prevents direct 
access to the struct members.  Or in some cases we'd remove an include of 
iperf.h from an existing module - main.c is an example, it should be using the 
API only.

Original issue reported on code.google.com by jef.posk...@gmail.com on 14 Aug 2013 at 7:15

[GoogleCodeExporter]

Original comment by jef.posk...@gmail.com on 14 Aug 2013 at 7:16

• Added labels: Milestone-future