This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: gcj System PRoperties documentation (Was: Throwable stack trace printing again)
- From: Tom Tromey <tromey at redhat dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: 27 Aug 2002 11:07:16 -0600
- Subject: Re: gcj System PRoperties documentation (Was: Throwable stack trace printing again)
- References: <1027719277.1819.54.camel@elsschot><15685.30002.216505.831464@cuddles.cambridge.redhat.com><1027972685.8318.17.camel@elsschot> <87ptwizqkd.fsf@fleche.redhat.com><1029709282.11219.15.camel@elsschot><1030431779.22377.5.camel@elsschot>
- Reply-to: tromey at redhat dot com
>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
Mark> * gcj.texi: Add chapter about System Properties.
Mark> The Throwable patch has gone in.
Mark> Is this documentation patch OK?
Mark> (I have CCed gcc-patches now.)
Sorry I haven't gotten to this yet.
Mark> +The runtime behaviour of the @code{libgcj} library can be modified by setting
Mark> +certain System properties. These properties can be compiled into the program
I think our standard is two spaces after a period.
Perhaps that's overly pedantic.
I think I would write "system properties" -- i.e., don't capitalize
"System". Or if you intended to refer to java.lang.System, then I'd
write @code{System}.
Mark> +A "|" separated list of package names that is used to find classes that
In Texinfo write @samp{|} instead of "|".
There are other cases like this.
Mark> +Wheter calls to unknown functions (class and method names are unknown)
Typo: "Whether" is missing an `h'. There are a couple of these.
Other than these things this patch is fine. Thanks a lot for doing
this; writing documentation seems to be everybody's least favorite
activity.
Tom