From ba53144974730a4a6fecc4ec120ad25eed91848e Mon Sep 17 00:00:00 2001
From: simonmar <unknown>
Date: Thu, 6 Apr 2000 10:45:11 +0000
Subject: [PATCH] [project @ 2000-04-06 10:45:11 by simonmar] add a note about
 POSIX compliance.

---
 docs/coding-style.html |   10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/coding-style.html b/docs/coding-style.html
index 6972000..2bcf715 100644
--- a/docs/coding-style.html
+++ b/docs/coding-style.html
@@ -61,6 +61,15 @@ We use ANSI C with some extensions.  In particular, we use:
 <li>#elsif, #error, #warning, ## and other cpp features
 </ul>
 
+<li> Our POSIX policy: try to write code that only uses POSIX (IEEE
+Std 1003.1) interfaces and APIs.  When you include <code>Rts.h<code>,
+<code>POSIX_SOURCE</code> is automatically defined for you before any
+system headers are slurped in, unless you define
+<code>NON_POSIX_SOURCE</code> prior to including <code>Rts.h</code>.
+A good C library will use the <code>POSIX_SOURCE</code> define to
+eliminate non-posix types and function prototypes, so the compiler
+should complain if you venture outside the POSIX spec.</li>
+
 <li>
 We use the following gcc extensions (see gcc documentation):
 <ul>
@@ -509,7 +518,6 @@ within Hugs.  Add this to your .emacs file.
     )
 </pre>
 
-
 </ul>
 
 <h2>CVS issues</h2>
-- 
1.7.10.4