llvm-project/llvm/lib/System/Unix
Chris Lattner 8bdd0fc7aa Fix bugpoint
llvm-svn: 19605
2005-01-16 04:23:22 +00:00
..
SUS Implementation of Process concept for SUSv2 platforms. 2004-09-11 04:54:06 +00:00
MappedFile.inc Rename Unix/*.cpp and Win32/*.cpp to have a *.inc suffix so that the silly 2005-01-09 23:29:00 +00:00
Memory.inc Rename Unix/*.cpp and Win32/*.cpp to have a *.inc suffix so that the silly 2005-01-09 23:29:00 +00:00
Path.inc Rename Unix/*.cpp and Win32/*.cpp to have a *.inc suffix so that the silly 2005-01-09 23:29:00 +00:00
Process.inc Rename Unix/*.cpp and Win32/*.cpp to have a *.inc suffix so that the silly 2005-01-09 23:29:00 +00:00
Program.inc Fix bugpoint 2005-01-16 04:23:22 +00:00
README.txt Fix a typo. 2004-08-26 07:43:33 +00:00
Signals.inc Rename Unix/*.cpp and Win32/*.cpp to have a *.inc suffix so that the silly 2005-01-09 23:29:00 +00:00
TimeValue.inc Make asctime_r work for HP/UX. 2005-01-14 00:50:50 +00:00
Unix.h For PR351: 2004-12-27 06:17:50 +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.