3c3
< % $Header: G:\MICROP\56FTWS0\RCS\learnc.tex 1.16 1996/03/13 16:31:49 Nick Exp $
---
> % $Header: G:\MICROP\56FTWS0\RCS\learnc.tex 1.16 1996/03/13 16:31:49 Nick Exp Nick $
103c103
< % $Header: G:\MICROP\56FTWS0\RCS\learnc.tex 1.16 1996/03/13 16:31:49 Nick Exp $
---
> % $Header: G:\MICROP\56FTWS0\RCS\learnc.tex 1.16 1996/03/13 16:31:49 Nick Exp Nick $
5131c5131
< (\Vf{PBDR}) to put these ports into submode~1X.}
---
> (\Vf{PBCR}) to put these ports into submode~1X.}
6016,6020c6016,6020
< You are familiar with the Edit/Compile/Download/Run procedure that
< you have used many times---once each time you create and run a program on
< the \FLIGHT microprocessor board.  See appendix~\vref{sec:ecdr}q
< for more information about the procedure for
< editing, downloading and running a program.
---
> You are familiar with the Edit/Compile/Download/Run procedure that you
> have used many times---once each time you create and run a program on
> the \FLIGHT microprocessor board.  See appendix~\vref{sec:ecdr} for
> more information about the procedure for editing, downloading and
> running a program.
6028a6029,6030
> Appendix~\vref{sec:errors} discusses the error messages from the
> compiler in more detail.
6775a6778
> \label{sec:errors}
6943a6947
> \index{error messages!\textsc{unresolved externals}|(}
6954a6959,6960
> \index{error messages!undeclared function|(}
> \index{undeclared function error message|(}
6978c6984,6989
< variables should be declared before they are used.
---
> variables should be declared before they are used.  This applies to
> ordinary library functions also.  For example, if you use @printf()@,
> you need to @#include <stdio.h>@ or you will get an \texttt{undeclared
> function} warning from the compiler.
> \index{undeclared function error message|)}
> \index{error messages!undeclared function|)}
6984a6996
> \index{error messages!\textsc{unresolved externals}|)}
6985a6998
> %@+
7015,7016c7028,7029
< {\Large ``FATAL''} and ``Bad''\e!  What shall we do?  Is a funeral
< director required at this stage?
---
> {\Large ``FATAL''} and {\large``Bad''}\e!  What shall we do?  Is a \ix{funeral
> director} required at this stage?
7027a7041,7062
> The problem happens because the program \file{cc68k.exe} calls many
> other programs; it decides which one to call by the extension of the
> filename (i.e., the part of the filename after the dot `\texttt{.}').
> If \file{cc68k.exe} does not recognise the extension, it seems to call
> the linker and hope that the linker can deal with it.  The error
> messages from the linker are sometimes not very helpful.
> 
> \index{Cannot Open File error message|(}
> \index{error messages!Cannot Open File|(}
> A similar problem can arise when you type:
> \begin{verbatim}
> cc68k leds
> \end{verbatim}
> The linker will complain, 
> \begin{verbatim}
> FATAL ERROR: (319) Cannot Open File leds.OBJ
> \end{verbatim}
> The solution to this problem is simply to put the `\file{.c}' at the
> end of the filename when you call \file{cc68k}.
> %@-
> \index{Cannot Open File error message|)}
> \index{error messages!Cannot Open File|)}
7182c7217
< \index{;@\Of{;} (semicolon)|(}
---
> \index{;@\Of{;} \ (semicolon)|(}
7214c7249
< \index{;@\Of{;} (semicolon)|)}
---
> \index{;@\Of{;} \ (semicolon)|)}
7384a7420,7422
> 
> Add: index of short, long, int, char unsigned char, types.
> Check have index, subscript.