This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch] java/(* Fix comment/doc typos.


Hi,

Committed as obvious.

Kazu Hirata

2005-04-04  Kazu Hirata  <kazu@cs.umass.edu>

	* gcj.texi: Fix a typo.
	* lang.c: Fix a comment typo.

Index: gcj.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/java/gcj.texi,v
retrieving revision 1.78
diff -u -d -p -r1.78 gcj.texi
--- gcj.texi	2 Apr 2005 02:26:39 -0000	1.78
+++ gcj.texi	4 Apr 2005 15:27:35 -0000
@@ -1653,7 +1653,7 @@ java::util::Hashtable *ht = new java::ut
 @node Memory allocation
 @section Memory allocation
 
-When allocting memory in @acronym{CNI} methods it is best to handle
+When allocating memory in @acronym{CNI} methods it is best to handle
 out-of-memory conditions by throwing a Java exception.  These
 functions are provided for that purpose:
 
Index: lang.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/java/lang.c,v
retrieving revision 1.170
diff -u -d -p -r1.170 lang.c
--- lang.c	23 Mar 2005 19:47:08 -0000	1.170
+++ lang.c	4 Apr 2005 15:27:35 -0000
@@ -801,7 +801,7 @@ merge_init_test_initialization (void **e
   does this by setting the DECL_INITIAL of the init_test_decl for that
   class, and no initializations are emitted for that class.
 
-  However, what if the method that is suppoed to do the initialization
+  However, what if the method that is supposed to do the initialization
   is itself inlined in the caller?  When expanding the called method
   we'll assume that the class initialization has already been done,
   because the DECL_INITIAL of the init_test_decl is set.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]