Compiler Errors

• The compiler is your friend.
• It's error messages are helpful advice, not complaints or admonishments.
• Its just not very tactful, that's all.

Read the Compiler Errors

Messages like :

linux3[77] % gcc -Wall -ansi sample.c
sample.c: In function `main':
sample.c:30: parse error before `printf'
sample.c:36: warning: control reaches end of non-void function
linux3[78] % 

Here are the lines of sample.c from line 26 to 36 :

   /* Display the largest integer entered */
   if(largest == 0)
   {
      printf("\nYou quit right away!  No integer to")
      printf(" display.\n");
   }
   else
   {
      printf("\nThe largest integer entered was %d.\n", largest);
   }
}

sample.c:30: parse error before `printf'

There is also a warning message:

sample.c:36: warning: control reaches end of non-void function

Instead of cutting or commenting out every line that comes up with an error, it's important to try to understand what's causing that error.

But How Do I Get My Editor To Tell Me What Line Number I'm On?

In xemacs, the command [ESC]-x line (press escape, press x, then type the word line and hit enter) will turn on the line numbering. The line you're on will appear on the bottom bar. Like this :

ISO8--**-XEmacs: sample.c  (C Font)----L30--All----------------

Alternatively, you can invoke the next line (^N) command with an argument, for example

u25n

goes down 25 lines.

In vi, the command [CTRL]->g (hold down the control key while pressing "g") will show you what line you are on. To jump to a line, type in the line number and then press "G".