llvm-project

History

Reid Spencer 1b13a7cdb8 * Use low-level unix I/O interface since we're on Unix. * Don't use variable length arrays (replaced with alloca) llvm-svn: 17901		2004-11-16 17:14:08 +00:00
..
SUS	Implementation of Process concept for SUSv2 platforms.	2004-09-11 04:54:06 +00:00
MappedFile.cpp	Fix bugs in class invariant	2004-11-14 22:07:50 +00:00
Memory.cpp	Provide a generic Unix implementation of the Memory concept.	2004-09-11 04:57:25 +00:00
Path.cpp	* Use low-level unix I/O interface since we're on Unix.	2004-11-16 17:14:08 +00:00
Process.cpp	Provide a generic unix implementation of the Process abstraction.	2004-09-11 04:56:56 +00:00
Program.cpp	Stop propagating method names that violate the coding standard	2004-11-05 22:15:36 +00:00
README.txt	Fix a typo.	2004-08-26 07:43:33 +00:00
Signals.cpp	Update for prototype changes	2004-11-14 22:09:22 +00:00
SysConfig.cpp	Actually define PreventCoreFiles in the sys namespace.	2004-08-31 17:53:41 +00:00
TimeValue.cpp	Per code review:	2004-11-16 06:22:17 +00:00
Unix.h	Forget strerror_r, it causes problems. Fix later when threading matters	2004-11-14 22:10:54 +00:00

README.txt

llvm/lib/System/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory 
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification 
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.