From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Pointers and DJGPP
Date: Thu, 19 Mar 1998 19:15:55 -0500
Organization: Two pounds of chaos and a pinch of salt.
Lines: 23
Message-ID: <3511B53B.403A@cs.com>
References: <199803190555 DOT VAA19201 AT adit DOT ap DOT net> <35111857 DOT 11BC9D3 AT mail DOT ucsm DOT edu DOT pe>
NNTP-Posting-Host: ppp210.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

rpinnell AT characato DOT ucsm DOT edu DOT pe wrote:
> 
> Well sorry it was a  general C question after all but is it possible to enable
> something in DJGPP to detect errors like this and give a warning on
> compilation.Richard Pinnell
> Arequipa Peru

The '-Wall' and '-O' command line options give you a great deal of
useful information.  '-Wall' turns on extra warning messages that often
indicate buggy code.  '-O' turns on optimizations, which can catch
things that '-Wall' can't catch by itself, such as uninitialized
variables.  For extremely drastic error checking, try also using
'-ansi', '-pedantic', '-W', and/or '-Werror'.  Each of these options and
more is described in detail in the gcc documentation ("info gcc
invoking").

-- 
---------------------------------------------------------------------
|      John M. Aldrich       | "Autocracy is based on the assumption|
|       aka Fighteer I       | that one man is wiser than a million |
|   mailto:fighteer AT cs DOT com   | men.  Let's play that over again,    |
| http://www.cs.com/fighteer | too.  Who decides?"   - Lazarus Long |
---------------------------------------------------------------------