On Mon, Apr 29, 2013 at 9:37 PM, Christopher Sean Morrison <[email protected]> wrote:
> Not just that you're going to reduce code, but what code, how, why, etc. Refactoring is not simply to reduce the LOC, it is to make the code easier to work with in the future. > Also, how will you ensure nothing is broken? I will use Google C++ test framework for unit testing as I have a working experience of it. http://avneetkhasla.wordpress.com/2013/04/12/google-c-testing-frameworkgoogle-test-gtest/ > I also recommend creating a patch so you know what you're getting into and so > we know > where your abilities are at reading code... ;) Submitted a patch. http://sourceforge.net/p/brlcad/patches/173/ We can reduce even more code in this patch, but it makes code difficult to maintain, I think. We do refactoring for four purposes : > That's great. Is there a reason you haven't considered a conversion project > instead? 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. -- Avneet Kaur www.avneetkhasla.wordpress.com ------------------------------------------------------------------------------ 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
