I saw something
similar to this in a test script:
#fdef Capybara:
#include
"A.h"
#include "B.h"
#include "B.h"
#else
#include
"B.h"
#endif
Fair enough. I can imagine that this was NOT the way this
conde snippet was checked in - it probably changed over time to what it is
now. I haven't yet dug into the history
of it.
That seems a bit
inefficient to me and I would prefer to change it to:
#fdef Capybara:
#include
"A.h"
#endif
#include "B.h"
#include "B.h"
Fewer lines and should perform the exact same includes.
But I won't make
this change and here is why:
- It may break. The odds are small, but why add risk where the system is currently working?
- It's a small benefit overall. Maybe 1/1000 of a second faster build times.
- It takes some amount of time to make the change, build, test it, get a code review, check it in, etc… I can't see any time savings for this change in the long run.
- A better fix than this one change would be a tool looking for this pattern in ALL our files. Then use the tool to make the change everywhere, and make the tool part of the regular code checks we perform constantly.
But considering #2
overall, even a tool would not pay for itself.
So I am leaving this as is for now and moving on to my next task.
(But if I have the
fortune of needing to edit that file, I will be sorely tempted to make this fix
at the same time :) )
Questions, comments,
concerns and criticisms always welcome,
John
No comments:
Post a Comment