2012/11/13 Pete Batard <p...@akeo.ie>
> On 2012.11.13 10:23, Toby Gray wrote:
> > I've been tempted to write a simple test application to do things
> > similar to this for a while now. Just a few for loops which call various
> > APIs many hundreds of times to help detect memory leaks.
>
> That would be nice. I see no issue adding such a test app to our samples.
>
> > The only thing
> > which has really stopped me is that I couldn't decide if it should be an
> > example (so live in examples/stress_test.c) or to create a new test
> > directory for test source.
>
> I'd say for now, if it's only one test app, examples will be just fine.
> But location doesn't matter vs content: we can always move it around at
> a later date if we feel like it.
>
I would use a test/ directory for programs used for tests (stress test in
this case).
These stress test programs should NOT be used as example by our users. We
should try to avoid possible confusion where we can.
It can be the beginning of a more complete test suite :-)
Bye
--
Dr. Ludovic Rousseau
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
