nobu	2015-12-02 11:36:58 +0900 (Wed, 02 Dec 2015)

  New Revision: 52849

  http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=52849

  Log:
    explicit_bzero.c: fix typos
    
    * missing/explicit_bzero.c (explicit_bzero): fix typos, probably.

  Modified files:
    trunk/missing/explicit_bzero.c
Index: missing/explicit_bzero.c
===================================================================
--- missing/explicit_bzero.c	(revision 52848)
+++ missing/explicit_bzero.c	(revision 52849)
@@ -64,9 +64,9 @@ void https://github.com/ruby/ruby/blob/trunk/missing/explicit_bzero.c#L64
 explicit_bzero(void *b, size_t len)
 {
     /*
-     * volatile is not enough if compiler have a LTO (link time
+     * volatile is not enough if the compiler has an LTO (link time
      * optimization). At least, the standard provides no guarantee.
-     * However, gcc and major other compiler never optimize a volatile
+     * However, gcc and major other compilers never optimize a volatile
      * variable away. So, using volatile is practically ok.
      */
     volatile char* p = (volatile char*)b;

--
ML: ruby-changes@q...
Info: http://www.atdot.net/~ko1/quickml/