diff options
author | Paul Fisher <rao@gnu.org> | 1999-03-06 20:02:23 +0000 |
---|---|---|
committer | Paul Fisher <rao@gnu.org> | 1999-03-06 20:02:23 +0000 |
commit | 08434fc554eb5289e545124d2ee95825358d2a38 (patch) | |
tree | 07ec1f56b73261e2bb5d481a5c4ba0a2edad7091 /doc | |
parent | e069449790109ba78cbe5327f781cf58f4d2f735 (diff) | |
download | classpath-08434fc554eb5289e545124d2ee95825358d2a38.tar.gz |
Update coding standards. Remove references to DejaGNU, and update
versions of required software.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/hacking.texinfo | 20 |
1 files changed, 7 insertions, 13 deletions
diff --git a/doc/hacking.texinfo b/doc/hacking.texinfo index 3c941094b..6ca10cb4d 100644 --- a/doc/hacking.texinfo +++ b/doc/hacking.texinfo @@ -257,13 +257,11 @@ familiarize yourself with the following tools: @item CVS 1.9 @item -automake 1.3 +automake 1.4 @item -autoconf 2.12 +autoconf 2.13 @item -dejagnu 1.3 -@item -libtool 1.2 +libtool 1.2d @item GNU m4 1.4 @item @@ -288,10 +286,6 @@ repository of all code in the Classpath system. Access to the repository requires an account. Contact Paul Fisher (@email{rao@@gnu.org}) for details. -@item dejagnu -A package for automating regression test suites for programs. Your -regression test package should work with this. - @item automake This tool automatically creates Makefile.in files from Makefile.am files. The Makefile.in is turned into a Makefile by autoconf. Why use @@ -332,10 +326,10 @@ The standards also specify various things like the install directory structure. These should be followed if possible. For Java code, please follow the -@uref{http://java.sun.com/docs/codeconv/html/CodeConventionsTOC.doc.html,Sun -programming standards}. As an exception, do not feel obligated to -following their bracket and indentation style if you consider it to be -wrong. +@uref{http://www.fsf.org/prep/standards_toc.html,GNU Coding Standards}, +with the exception of naming conventions. Please follow +@uref{http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html,Sun's +naming conventions}. For documentation comments, please follow @uref{http://java.sun.com/products/jdk/javadoc/writingdoccomments.html,How |