6282 ONBLD man pages not pbchk clean
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>

*** 18,36 ****
  .\" fields enclosed by brackets "[]" replaced with your own identifying
  .\" information: Portions Copyright [yyyy] [name of copyright owner]
  .\"
  .\" CDDL HEADER END
  .\"
! .TH jstyle 1ONBLD "22 November 2005"
  .SH NAME
  .I jstyle
  \- check for some common stylistic errors in Java source files
  .SH SYNOPSIS
  \fBjstyle [-chptvC] [file...]\fP
- .LP
  .SH DESCRIPTION
- .IX "OS-Net build tools" "jstyle" "" "\fBjstyle\fP"
  .LP
  .B jstyle
  inspects Java source files (*.java) for common stylistic errors.  It
  is similar to
  .BR cstyle (1ONBLD)
--- 18,34 ----
  .\" fields enclosed by brackets "[]" replaced with your own identifying
  .\" information: Portions Copyright [yyyy] [name of copyright owner]
  .\"
  .\" CDDL HEADER END
  .\"
! .TH JSTYLE 1ONBLD "Nov 22, 2005"
  .SH NAME
  .I jstyle
  \- check for some common stylistic errors in Java source files
  .SH SYNOPSIS
  \fBjstyle [-chptvC] [file...]\fP
  .SH DESCRIPTION
  .LP
  .B jstyle
  inspects Java source files (*.java) for common stylistic errors.  It
  is similar to
  .BR cstyle (1ONBLD)
*** 41,51 ****
  .I cannot
  be checked for; just because your code is
  .BR jstyle (1ONBLD)
  clean does not
  mean that you've followed Sun's Java style.  \fICaveat emptor\fP.
- .LP
  .SH OPTIONS
  .LP
  The following options are supported:
  .TP 4
  .B \-c
--- 39,48 ----
*** 52,71 ****
  Check continuation line indentation inside of functions.  Sun's C style
  states that all statements must be indented to an appropriate tab stop,
  and any continuation lines after them must be indented \fIexactly\fP four
  spaces from the start line.  This option enables a series of checks
  designed to find contination line problems within functions only.
- .LP
  .TP 4
  .B \-h
  Performs heuristic checks that are sometimes wrong.  Not generally used.
- .LP
  .TP 4
  .B \-p
  Performs some of the more picky checks.  You should generally use this.
- .LP
- .LP
  .TP 4
  .B \-t
  Insists on indentation with tabs.  Because of the depth of nested blocks
  that Java requires, and the commonality of long identifiers, tab
  indentation in Java code is not always useful, assuming that tabs are fixed
--- 49,64 ----
*** 72,109 ****
  at eight columns and that maximum line length is fixed at eighty columns,
  so this option is not on by default.  If you choose to consider tabs to be
  four columns wide (not acceptable for ON), or are writing simple enough
  code that the nesting is not very deep, this option might be useful.
  Otherwise, avoid it.
- .LP
  .TP 4
  .B \-v
  Verbose output; includes the text of the line of error.
- .LP
  .TP 4
  .B \-C
  Ignore errors in header comments (i.e., block comments starting in the
  first column).  Not generally used.
- .LP
- .LP
  .SH NOTES
  .LP
  The jstyle rule for the OS/Net consolidation is that all new files must
  be
  .B -p
  clean.  For existing files, the following invocations are
  run against both the old and new files:
- .LP
  .TP 4
  .B "jstyle file"
- .LP
  .TP 4
  .B "jstyle -p file"
  .LP
  If the old file gave no errors for one of the invocations, the new file
  must also give no errors.  This way, files cannot become unclean.
- .LP
  .SH BUGS
  .LP
  .BR jstyle (1ONBLD)
  cannot disambiguate Java generic type parameters or
  arguments that span multiple lines from relational operators.  For example:
--- 65,95 ----