Clear up some confusion over ANSI vs ISO C support

Closes #890

Author: wsfulton

exec.ht

@@ -59,7 +59,7 @@ to your application.  If anything, it's much more of a rapid
 application development and prototyping tool.  Specifically:
 
 <ul>
-<li><p><b>ANSI C/C++ syntax</b>.  SWIG parses ANSI C++ that has been
+<li><p><b>ISO C/C++ syntax</b>.  SWIG parses ISO C++ that has been
 extended with a number of special directives.  As a result, interfaces
 are usually built by grabbing a header file and tweaking it a little
 bit.  This particular approach is especially useful when the

history.ht

@@ -34,7 +34,7 @@ newer SWIG releases.
 
 <li>February 11, 2000. SWIG1.3 alpha released.   This is the first in
 a series of releases that slowly migrate most of SWIG's implementation
-back to ANSI C.
+back to ISO C.
 
 <li>March 1, 2000. SWIG1.3a2 released.
 <li>June 18, 2000. SWIG1.3a3 released.

myths.ht

@@ -7,11 +7,11 @@ Here are some common misconceptions about SWIG that have occasionally
 appeared on other web pages and in articles--especially those that
 describe older SWIG versions.
 
-<h4><font color="#ff0000">Myth: SWIG only really works with ANSI C</font></h4>
+<h4><font color="#ff0000">Myth: SWIG only really works with ISO C</font></h4>
 
 <h4>Fact:</h4>
 
-SWIG <em>does</em> provide wrapping support for all of ANSI C.  However, SWIG has
+SWIG <em>does</em> provide wrapping support for all of ISO C.  However, SWIG has
 also included C++ support since its initial release in 1996.   To be fair, early
 SWIG releases had limitations, but C++ support has continually improved with
 each SWIG release.