On Fri, Jul 19, 2013 at 5:18 AM, Graham Reeds <[email protected]>wrote:
> Though in my opinion there are serious issues with the version on Git hub,
> the most serious is the hard coded paths.
>
Another user pointed this out to me on Twitter a few days ago, where my
response was to write up a bug and/or pull to fix, but unfortunately that
individual has not done so. I wrote up
https://github.com/unittest-cpp/unittest-cpp/issues/47 just now. I
generated those projects using CMake, forgetting that one aspect of CMake.
Keeping project files up-to-date is a maintenance issue that I'd like to
see some discussion on. See
https://github.com/unittest-cpp/unittest-cpp/issues/42.
What other serious issues are there? Please write tickets for them!
> Speaking of which I was going to rename the vs projects directory to
> just projects and move the mac into there too.
>
That would be fine, the choice to separate them was somewhat arbitrary.
> Final change is to rename the UnitTest++ directory to src.
>
The change from src to UnitTest++ was done as part of addressing an earlier
issue. What issue does changing it back address?
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
