Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Small refactoring in build system
#2
Good job Smile

I have only one minor complaint to make: the "main" in names of builds "colobot-gold-main-dev*" is a bit confusing. I would name them simply "colobot-gold-dev*".

Now that we have our own CI server, we can use it to do some cool stuff as Jenkins has a number of plugins to display charts or tables of data. We could use it to keep track of some statistics showing our refactoring progress in code. We could add for example:
- number of TODOs left in code
- number of "naked" new/delete
- number of functions in old style, declaring variables at the beginning of function
- number of functions longer than say 200 lines
- number of violations of our coding style, like wrongly named variables

As to the problem how to generate this data, I've been playing recently with Clang's LibTooling framework. It can be used to perform static analysis on our source code using Clang's internal parser and allowing access to the generated syntax tree. When I find more time, I'll create a tool that generates at least some of these statistics.


Messages In This Thread
Small refactoring in build system - by krzys_h - 06-22-2015, 09:37 PM
RE: Small refactoring in build system - by piotrdz - 06-24-2015, 08:29 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)