Re: File listing supported properties in GNU classpath
Hi Wolgang, On Mon, 2006-03-13 at 20:30 +0100, Wolfgang Baer wrote: > how about adding a new file which lists all our supported properties. > Currently this information about our properties (for swing, graphics2D, > rmi, corba) are spread over all parts of the NEWS file. Good idea. There is also a (probably also incomplete) list of properties at http://gcc.gnu.org/onlinedocs/gcj/System-properties.html Maybe you could start with that (see gcj.texi in the gcc sources)? Cheers, Mark signature.asc Description: This is a digitally signed message part
Re: File listing supported properties in GNU classpath
> "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes: >> how about adding a new file which lists all our supported properties. >> Currently this information about our properties (for swing, graphics2D, >> rmi, corba) are spread over all parts of the NEWS file. Mark> Good idea. There is also a (probably also incomplete) list of properties Mark> at http://gcc.gnu.org/onlinedocs/gcj/System-properties.html Mark> Maybe you could start with that (see gcj.texi in the gcc sources)? Yeah, this is a good idea. It seems like something worth automating; either automating the extraction like javadoc, or at least automated checking so that we don't have documentation regressions. Tom
Re: File listing supported properties in GNU classpath
On Mar 13, 2006, at 3:42 PM, Tom Tromey wrote: "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes: how about adding a new file which lists all our supported properties. Currently this information about our properties (for swing, graphics2D, rmi, corba) are spread over all parts of the NEWS file. Mark> Good idea. There is also a (probably also incomplete) list of properties Mark> at http://gcc.gnu.org/onlinedocs/gcj/System-properties.html Mark> Maybe you could start with that (see gcj.texi in the gcc sources)? Yeah, this is a good idea. It seems like something worth automating; either automating the extraction like javadoc, or at least automated checking so that we don't have documentation regressions. The Jessie library uses a bunch of Security properties to control its run-time behavior; these are documented in the Jessie manual, but should be put into Classpath's documentation now. GNU Crypto also uses a few properties, but in their own file. These should also be documented, or maybe deprecated in favor of System or Security properties.
Re: File listing supported properties in GNU classpath
Hi all, thanks for the input and the infos where to look for properties. I will put all the properties together and post them for review. Don't know exactly when I find time but I hereby assign this task to me :-) Wolfgang Casey Marshall wrote: > On Mar 13, 2006, at 3:42 PM, Tom Tromey wrote: > >>> "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes: >> >> how about adding a new file which lists all our supported properties. Currently this information about our properties (for swing, graphics2D, rmi, corba) are spread over all parts of the NEWS file. >> >> >> Mark> Good idea. There is also a (probably also incomplete) list of >> properties >> Mark> at http://gcc.gnu.org/onlinedocs/gcj/System-properties.html >> Mark> Maybe you could start with that (see gcj.texi in the gcc sources)? >> >> Yeah, this is a good idea. It seems like something worth automating; >> either automating the extraction like javadoc, or at least automated >> checking so that we don't have documentation regressions. >> > > The Jessie library uses a bunch of Security properties to control its > run-time behavior; these are documented in the Jessie manual, but > should be put into Classpath's documentation now. > > GNU Crypto also uses a few properties, but in their own file. These > should also be documented, or maybe deprecated in favor of System or > Security properties. >
