This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I have to "convince" my developers that they clean up / fix their code. Until then I have to stick to gcc-3.3.3 whcih allows such nasty stuff.
Yep. It's an education problem. I'd suggest running a nightly build with the new tools, and emailing errors to the developer who wrote the code that doesn't compile. I have a script that does this by looking up the line of the error in Perforce to see who checked in that line. The whole thing runs from a cron job. It's a pain to keep it running, but it's worth it.
-- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |