/[classpath]/classpath/doc/hacking.texinfo
ViewVC logotype

Diff of /classpath/doc/hacking.texinfo

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.36 by ziga, Mon Jul 4 14:31:01 2005 UTC revision 1.37 by aluchko, Fri Jul 8 16:01:40 2005 UTC
# Line 458  java.lang.StrictMath. Line 458  java.lang.StrictMath.
458  @chapter Programming Standards  @chapter Programming Standards
459    
460  For C source code, follow the  For C source code, follow the
461  @uref{http://www.fsf.org/prep/standards_toc.html,GNU Coding Standards}.  @uref{http://www.gnu.org/prep/standards/,GNU Coding Standards}.
462  The standards also specify various things like the install directory  The standards also specify various things like the install directory
463  structure.  These should be followed if possible.  structure.  These should be followed if possible.
464    
465  For Java source code, please follow the  For Java source code, please follow the
466  @uref{http://www.fsf.org/prep/standards_toc.html,GNU Coding  @uref{http://www.gnu.org/prep/standards/,GNU Coding
467  Standards}, as much as possible.  There are a number of exceptions to  Standards}, as much as possible.  There are a number of exceptions to
468  the GNU Coding Standards that we make for GNU Classpath as documented  the GNU Coding Standards that we make for GNU Classpath as documented
469  in this guide.  We will hopefully be providing developers with a code  in this guide.  We will hopefully be providing developers with a code
# Line 484  guidelines more tailored to GNU Classpat Line 484  guidelines more tailored to GNU Classpat
484    
485  Here is a list of some specific rules used when hacking on GNU  Here is a list of some specific rules used when hacking on GNU
486  Classpath java source code. We try to follow the standard  Classpath java source code. We try to follow the standard
487  @uref{http://www.gnu.org/prep/standards_23.html,GNU Coding Standards}  @uref{http://www.gnu.org/prep/standards/,GNU Coding Standards}
488  for that. There are lots of tools that can automatically generate it  for that. There are lots of tools that can automatically generate it
489  (although most tools assume C source, not java source code) and it  (although most tools assume C source, not java source code) and it
490  seems as good a standard as any. There are a couple of exceptions and  seems as good a standard as any. There are a couple of exceptions and

Legend:
Removed from v.1.36  
changed lines
  Added in v.1.37

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26