[GRASS5] Towards a 5.1.0 experimental release

[H Bowman]

On Sat, 17 May 2003 19:23:55 +0200
"Markus Neteler" <neteler at itc.it> wrote:

> > >  1. Uniform coding style.
[...]
> > > Step 1 boils down to choosing a set of switches for the "indent"
> > > program, then running indent on all source files.
> > 
> > Are you absolutely sure that this improves the situation
> > in all cases? Please suggest a set of switches that Radmin
> > and Markus agree with.
> 
> I have already suggested this month ago and proposed to use
> the indent rule used by the Apache people (see grass5 archive,
> can't find the ref now).
> If you look at lib/image3/ you see an absolute nightmare of
> code layout.


Is this decided? (aka any objections?)
If it is, can it be added to the SUBMITTING file?

Apache coding style:
  http://www.apache.org/dev/styleguide.html

"This style can be generated with the following arguments to GNU indent:"
-i4 -npsl -di0 -br -nce -d0 -cli0 -npcs -nfc1


The reference to the "GNU coding standards" in SUBMITTING Rule #2 would
need to be qualified as GNU's section 5.1 presents a different standard.

Even if indent isn't run now, at least new & modified code could be
consistent..

=--=

> >  7. Consistent use (or not) of "cmd" subdirectory.

Is/was there any useful reason to use a cmd directory for modules or
is this just a historical leftover? Add answer to Rule #2 of SUBMITTING?
src/raster/r.example/cmd/main.c or src/raster/r.example/main.c ??



thanks,
Hamish