In a maze of scripts and Makefiles and scripts generating Makefiles and scripts generating scripts that call make, euphemistically called "a custom buildsystem", hunting down the right 'make' to change into 'make -d' can take a while.
That sounds like you're not doing sub-makes with $(MAKE), which would have passed down the -d automatically. See http://www.gnu.org/software/make/manual/html_node/MAKE-Variable.html#MAKE-Variable and http://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html#Options_002fRecursion
Does anyone know if MS Windows has introduced a UT internal time yet? If not, then we can reliably predict that such bugs will continue to plague their users.
According to an old MS guy , Windows NT stores UTC time internally but maintains the BIOS in local time. 1. http://blogs.msdn.com/b/oldnewthing/archive/2004/09/02/224672.aspx
Hiring standards vary according to the team because the needs of the team vary according to the team and according to what that person is going to be doing.
Just to play Devil's Advocate, what if the team was incompetent? It's not unheard of where all the good people leave the team, leading to hiring choices for similarly, incapable new employees.
:= was originally an ALGOL 58 feature, but I digress. The real problem is not with operator ==, but with C allowing assignment in the conditional part of if statements.
The new assignment operator ":="
Oh look, someone revived the Clipper dBASE compiler / Pascal syntax.
No, someone revived the the ALGOL 58 syntax (yes, that is 1958) . Everything old will be new again
Any program which runs right is obsolete.