Re: [Bug-indent] [GNU indent] errors, comments, etc.

[david ingamells]

Antoine,
A quick answer to a few of your questions.
I'll work through your suggestions for improvement and other questions when I 
get time - thank you for these.

1) http://www.xs4all.nl/~carlo17 is obsolete. Use the documentation 
distributed with indent itself. This is available as html, info or man.
3) What exactly are the differences?
20) you can use the environment variable INDENT_PROFILE to give the name of 
the profile file. Alternatively you can invoke indent via a personal or 
team-managed script and put the options explicitly in the actual call to the 
executable.

David.

On Monday 28 October 2002 8:35 am, address@hidden wrote:
> Hi,
>
> Here are a few comments about GNU indent version 2.2.8.
>
> Best regards,
> Antoine Trux
> Helsinki, Finland
>
>
>  1) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17, in the
> description of option `-cbin': "N spaces"
>     =>
>     "n spaces" (with "n" in italics; compare with, for example, option
> `-cn')
>
>  2) Is there a way to get:
>       char* x;
>     instead of:
>       char *x;
>     ?
>
>  3) Is there a way to get:
>       void
>       foo(int   a,
>           char *b)
>       {
>       }
>     instead of:
>       void
>       foo(int a,
>           char *b)
>       {
>       }
>     ?
>
>  4) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC12:
>     "longer then"
>     =>
>     "longer than"
>
>  5) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17, option
> `-bfda' is not listed in alphabetical order.
>
>  6) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17, options
> `-pin' and `-pmt' are not formatted like the other options ("See
> section..." not on a separate line).
>
>  7) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17, options
> `-cin' and `-pin' should refer to section 1.8, not to section 1.6.
>
>  8) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17, options
> `-cdw', `-ce', `-ncdw', and `nce' should refer to section 1.6, not to
> section 1.5.
>
>  9) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC11:
>     The option `-ipN' can be used to set the extra offset per paren.
>     =>
>     The option `-pin' can be used to set the extra offset per paren.
>
> 10) The description of option `-sbin' is missing from the first part of
> http://www.xs4all.nl/~carlo17/indent/indent.html (that is, from section "1.
> The indent Program").
>
> 11) About defaults:
>     - Some options have their default documented only in the main section
> ("1. The indent Program "), not in
> http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17. Examples: `-c',
> `-bli'. - Not all options have their default documented.
>
> 12) Currently, there is always a "common style" in use (GNU style by
> default). I think it would be clearer if: - there were an option to disable
> all common styles,
>     and:
>     - each option had a well-documented default.
>
> 13) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC17, option
> `-ncdw': Do not cuddle } and the while of a do {} while;.
>     =>
>     Do not cuddle `}' and the while of a `do {} while;'.
>
> 14) In several places:
>     '('
>     =>
>     `('
>     and:
>     ')'
>     =>
>     `)'
>
> 15) `--blank-before-sizeof' and `Bill-Shannon' are missing from section
> "Options' Cross Key".
>
> 16) When option `--verbose' is in use:
>     - part of the verbose output ("Line broken") goes to stderr,
>     - part of the verbose output (statistics) goes to stdout.
>     Wouldn't it be more appropriate to redirect all the verbose output to
> stderr?
>
> 17) Couldn't get option `-pin' to work. Can you confirm that it works?
>
> 18) In http://www.xs4all.nl/~carlo17/indent/indent.html#SEC8:
>     The exception to this a comment
>     =>
>     The exception to this is a comment
>
> 19) indent breaks long lines according to option `--line-lengthn'. This
> includes lines containing function calls. Is it possible to get indent to
> work in such a way that:
>     a) a line containing a function call that fits in the limit set by
> option `--line-lengthn' is not broken, and:
>     b) a line containing a function call that doesn't fit in the limit set
> by option `--line-lengthn' is broken, and each argument appears on its own
> line ?
>     For example, with `--line-length20', we get:
>       {
>         foo(a, c, e, f);
>       }
>     but we get:
>       {
>         foo(a, c, e, f,
>             g);
>       }
>     How to get:
>       {
>         foo(a,
>             c,
>             e,
>             f,
>             g);
>       }
>     instead?
>
>
> _______________________________________________
> Bug-indent mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-indent

-- 
David Ingamells
address@hidden
+31 (0)13 509 3388     (home)
+31 (0)61 501 0947 (mobile)