# HG changeset patch
# User Jordi Gutiérrez Hermoso <jordigh@octave.org>
# Date 1349440139 14400
# Node ID c9844b82945f2da45a8a9d8eb9c39985013b5d78
# Parent  dbc6b6b18286513ace738688c43dcc3db2799071
reformat interesting comment

diff --git a/libinterp/octave-value/ov-ch-mat.cc b/libinterp/octave-value/ov-ch-mat.cc
--- a/libinterp/octave-value/ov-ch-mat.cc
+++ b/libinterp/octave-value/ov-ch-mat.cc
@@ -152,12 +152,11 @@
   return retval;
 }
 
-// The C++ standard guarantees cctype defines functions, not macros
-// (and hence macros *CAN'T* be defined if only cctype is included)
-// so there's no need to f*ck around.
-// The exceptions are isascii and toascii, which are not C++.
-// Oddly enough, all those character functions are int (*) (int), even
-// in C++.  Wicked!
+// The C++ standard guarantees cctype defines functions, not macros (and
+// hence macros *CAN'T* be defined if only cctype is included) so
+// there's no need to fuck around. The exceptions are isascii and
+// toascii, which are not C++. Oddly enough, all those character
+// functions are int (*) (int), even in C++. Wicked!
 static inline int xisascii (int c)
 { return isascii (c); }