Annotated edit history of
-Wall version 8, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 6 |
AristotlePagaltzis |
1 |
When running [gcc(1)], [-Wall] is the [CommandLine] option that enables all warnings. Generally the first thing people will look for when debugging or helping others with [C]/[C++] code is that it compiles with [-Wall]. |
| |
|
2 |
|
| 8 |
SpellingMan |
3 |
[-Wall] warns about a great many things which are normally harmless in normal circumstances but can be dangerous at others. __-pedantic__ also warns against things that are technically wrong but cannot lead to problems for [gcc(1)] and __-pedantic-errors__ issues errors for such quibbles. __-pedantic__ and __-pedantic-errors__ are not usually used unless the code is being written with the intention of porting it to exotic hardware, as a last ditch attempt to find an elusive bug or as a method of evaluating the quality of code (StuartYeates always uses these flags when marking [C]/[C++] assignments). |
| 6 |
AristotlePagaltzis |
4 |
|
| 7 |
StuartYeates |
5 |
It is often a good idea to add [-Wall] to your __CFLAGS__ environment variable. The second thing to do after adding [-Wall] is to add __-g__ so you can get debugging symbols when your program crashes. Unlike [-Wall], __-g__ can effect the RunTime performance of the generated programs so is not recommended when building core system components on a production system. |
| 6 |
AristotlePagaltzis |
6 |
|
| |
|
7 |
Many programmers have a line similar to |
| |
|
8 |
export CFLAGS="-Wall -g" |
| |
|
9 |
in their __.profile__. |
