[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] compiler warnings
|
+1
I have adopted the habit of clearing all warnings before checking in classes
that I'm working on. Warnings do point out problems and at the very least
tell you when you've got ugly code.
Cheers,
Doug Schaefer
QNX Software Systems
Eclipse CDT Project Lead
http://cdtdoug.blogspot.com
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Ploett, Norbert
Sent: Monday, August 28, 2006 7:16 AM
To: CDT General developers list.
Subject: AW: [cdt-dev] compiler warnings
+1 from me :-)
I am a fan of warning-free code too and I'll try to keep all those plug-ins
clean which are clean.
Remind me if I should overlook something.
Bye
Norbert
-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Schorn, Markus
Gesendet: Montag, 28. August 2006 11:40
An: CDT General developers list.
Betreff: [cdt-dev] compiler warnings
Hi,
a month ago I fixed all warnings in the plugins 'org.eclipse.cdt.ui' and
'org.eclipse.cdt.refactoring'. I have also created project specific
preferences for the compiler errors/warnings, which are shared via CVS.
So the projects should be free of warnings in your workspace too.
Please help in keeping the projects free of warnings, it helps in
detecting problems early.
I did not do the same for the remaining plugins, because I do not know
enough about the code I'd be changing. It'd be a great thing to have a
warning free code base, though.
Markus.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
