On 30/05/2013 15:22, Ulrik Sandborg-Petersen wrote: >> /maintain -- development&debug scripts, C testing, etc. >> /maintain/data -- data for testing, fake language corpus and >> eventually its pre-trained models, etc. > > Why not call it /test and simply have tests in there? That way, the > purpose of the directory is clear by its name.
I think /tests should be reserved to "make check" scripts and data. Other stuff should stay in some other places. > I believe we have so few development scripts (valgrind.sh, rmfiles.sh, > autogen.sh) that they might as well stay in the root directory. But > again, I am not going to be dogmatic about this. Let's keep them there. >> /src -- should only keep the source of the distributed programs; >> acopost_test should be moved to /maintain > > Before we move acopost_test.c, we need to think it through carefully. > > Moving acopost_test.c to a different directory would entail: > > 1) Having to > > a) #include files with -I../src in the /test (or /maintain) directory, > or else > b) move all headers to an /include directory. > > 2) Having to create a convenience library, src/libacopost.a, which > acopost_test.o could link against, with the .o files being tested. > > > What do you think? Is this complexity worth the clarity/purity that > comes from moving acopost_test.c? Actually it would be possible to avoid the second point, but I also see not much benefit in moving this file right now. ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ acopost-devel mailing list acopost-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acopost-devel
