On Fri, Jul 19, 2013 at 8:18 AM, Graham Reeds <graham.re...@gmail.com>wrote:
>
> > The change from src to UnitTest++ was done as part of addressing an
> earlier issue. What issue does changing it back address?
>
> It offends my sensibilities:-)
>
> What earlier issue was there?
>
There are some users that download the project and use it in-place. As
such, if the folder is named src, then they either have to:

a) Add the src folder to their include path. This causes information loss,
because includes don't have a meaningful path prefix, or
b) Add the download folder to their include path. This maintains the
information, but now they have to use #include "UnitTest++/src/header.h", or
c) Do symbolic linking to get a more meaningful path prefix.

Yes there are numerous ways around 1 and 2 (including 3), but actually
changing the project is a low-friction way that doesn't hurt anybody else,
aside from their sensibilities. :) The other plus of this change is that
now unit tests can include UnitTest++/header.h instead of using relative
paths, so they serve as more illustrative examples.

A more typical arrangement, of course, is to have a separate 'src' folder,
and a separate 'include/UnitTest++' folder. This is what I would like to
convert to soon.

>  I will also do a nicer version of the money example as that is very
> scrappy and doesn't exactly promote best practices.
>
Great, I'd love to see it. Preferably in GitHub-flavored Markdown so we can
put it on the github wiki.
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
unittest-cpp-devel mailing list
unittest-cpp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel

Reply via email to