Print this page
6205 onbld manuals should be declared as 1onbld
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>
@@ -1,6 +1,6 @@
-jstyle(1) User Commands jstyle(1)
+jstyle(1ONBLD) illumos Build Tools jstyle(1ONBLD)
NAME
jstyle - check for some common stylistic errors in Java source files
@@ -8,16 +8,16 @@
SYNOPSIS
jstyle [-chptvC] [file...]
DESCRIPTION
jstyle inspects Java source files (*.java) for common stylistic errors.
- It is similar to cstyle(1) in that it attempts to check for the style
- documented in /shared/ON/general_docs/cstyle.ms.pdf, although by
+ It is similar to cstyle(1ONBLD) in that it attempts to check for the
+ style documented in /shared/ON/general_docs/cstyle.ms.pdf, although by
necessity is modified to work with Java-specific constructs. Note that
there is much in that document that cannot be checked for; just because
- your code is jstyle(1) clean does not mean that you've followed Sun's
- Java style. Caveat emptor.
+ your code is jstyle(1ONBLD) clean does not mean that you've followed
+ Sun's Java style. Caveat emptor.
OPTIONS
The following options are supported:
-c Check continuation line indentation inside of functions. Sun's C
@@ -58,17 +58,18 @@
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.
BUGS
- jstyle(1) cannot disambiguate Java generic type parameters or arguments
- that span multiple lines from relational operators. For example:
+ jstyle(1ONBLD) cannot disambiguate Java generic type parameters or
+ arguments that span multiple lines from relational operators. For
+ example:
private class Foo<A extends Bar,
B extends Bar> { ...
is flagged as two lines with missing spaces around relational
operators.
- 22 November 2005 jstyle(1)
+ 22 November 2005 jstyle(1ONBLD)