Re: The source file culture

[David Smead <smead@...>]

Gcc will do what you tell it to do.  Some people ignore warnings from gcc, 
but that's ill advised.  The first error as you mention is always 
informative, and the only one you should bother looking at.  Here's what I 
use to treat warnings as errors, and to stop after the first error.

For compile only - you probably need some include dirs and libs.
gcc  -c -ggdb -Wall -Werror -Wfatal-errors

To link:
gcc -o

These are in a Makefile, or course, with all of its beauty! And don't 
overlook the wonder of pkg-config.

David Smead
www.amplepower.com


On Tue, 8 Sep 2009, Jeff Pohlmeyer wrote:

> Date: Tue, 8 Sep 2009 01:27:08 -0500
> From: Jeff Pohlmeyer <yetanothergeek@gmail.com>
> Reply-To: Lua list <lua@bazar2.conectiva.com.br>
> To: Lua list <lua@bazar2.conectiva.com.br>
> Subject: Re: The source file culture
>
> On Sep 8, 2009 Jacques Chester wrote:
> > On 08/09/2009, at 7:45 AM, Vaughan McAlley wrote:
>
> > > error messages that might as well be written in Sumerian cuneform,
>
> > At the risk of inciting a flamewar, this is really GCC's fault,
> > not Lua's. ICC and Clang/LLVM, for example, give very helpful
> > error messages.
>
> Actually, the  *first*  error message printed by gcc is usually quite
> helpful, the problem is with the 6000 lines of useless garbage it
> vomits up after that :-)
>
>
> At least that's been my experience.
>
>
> - Jeff