On May 01, 2013, at 05:34 AM, Avneet Kaur <[email protected]> wrote:

Refactoring is not simply to reduce the LOC, it is to make the code
easier to work with in the future.

Sure, but you still should speak to what code, how, and why in your proposal.

I will use Google C++ test framework for unit testing as I have a
working experience of it.

You should look at our existing test infrastructure as a starting point (and speak to how).  If your proposal involves Google's framework, you'll need to explain how the two are going to co-exist and complement each other.

Refactoring the code is a challenging task.
I would prefer to proceed with this rather than DXF for the sake of my
current interests as
well as from learning point of view.

Fair enough.  Just keep in mind that the more generic and general the idea, the more detail and planning that is required up front in the proposal.  Targeted projects tend to be self-guided and self-explanatory.  General projects like refactoring need to have specific goals identified and be planned out in detail.

Sean

------------------------------------------------------------------------------
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
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to