X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fcoding-style.html;fp=docs%2Fcoding-style.html;h=2bcf715470036b7aad119b2331094b0fd564eb27;hb=ba53144974730a4a6fecc4ec120ad25eed91848e;hp=6972000f13219b1aeeead5f250cd8dbf7f5e8a20;hpb=461cddc13013a0f77147d7e47d4e1b25668c34f2;p=ghc-hetmet.git

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>