Received: (from majordom@localhost)
	by hyperreal.org (8.8.5/8.8.5) id RAA29598;
	Mon, 15 Sep 1997 17:08:01 -0700 (PDT)
Received: from twinlark.arctic.org (twinlark.arctic.org [204.62.130.91])
	by hyperreal.org (8.8.5/8.8.5) with SMTP id RAA29594
	for <new-httpd@apache.org>; Mon, 15 Sep 1997 17:07:57 -0700 (PDT)
Received: (qmail 18004 invoked by uid 500); 16 Sep 1997 00:07:31 -0000
Date: Mon, 15 Sep 1997 17:07:31 -0700 (PDT)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: indent, line splitting?
In-Reply-To: <Pine.LNX.3.95dg3.970915165851.8104Q-100000@twinlark.arctic.org>
Message-ID: <Pine.LNX.3.95dg3.970915170513.8104R-100000@twinlark.arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

I'm also finding that indent sometimes (but not always) totally mutates
switch statements.  It indents the case labels sometimes, and then lines
the code up with that.  But not all the time ... and we do specify -cli0
which should mean no indenting of the case statement.

Also on alloc.c it totally screws up because it does not understand va_arg
that well -- watch out for this.  I had to change:

    va_arg(ap, char *)

to:
    
    va_arg(ap, char_star)

and then reverse the change after running indent.

I just mention these things to dispel the notion that we can do this
periodically or on any automated basis.  indent is just not perfect
technology.

Dean

On Mon, 15 Sep 1997, Dean Gaudet wrote:

> Shouldn't our indent settings be doing line splitting?  They don't seem to
> be for me.
> 
> % indent --version
> GNU indent 1.9.1
> 
> Dean
> 
>