On 04/10/2012 06:44 PM, Timothy Pearson wrote: > I really wonder why gcc can't leave well enough alone sometimes...we can't > be the only large project affected by this change... It has become an annual tradition for gcc to break things this time of year. Recall roughly a year ago and gcc 4.5.2 which prompted running through the code to add '#include <cstddef.h>' throughout and redoing all the foo::foo(a) designations to foo(a)? Generally the gcc changes are to provide for the future, unfortunately not giving that much weight to the past. No we are not the only large project affected, but we are hit especially hard due to the small manpower-to-codebase_size of this project. Where other large projects, k4, gnome, etc.. may have hundreds of developers to help with changes, we have a relative few. Somehow -- it always gets done :-) If there were more time/manpower available, we would have the luxury of comparing the current c++ coding standards to the current code as we work through the gcc 4.7 changes -- that would hopefully eliminate or lesson the 2013 rat-race when gcc 4.8 comes out :-) -- David C. Rankin, J.D.,P.E.