llvm-6502/lib/Support/Unix
Chandler Carruth 6a40db40ee Eric thought that Darwin was right to use -1 consistently rather than
leaving this undefined, and despite the sentence in the standard that
seems to require it, I'll cede the point and assume its a bug in the
wording. Other parts of POSIX regularly allow for things to be -1
instead of undefined, this should too. Makes things more consistent too.

This should have to real impact for folks though.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@171574 91177308-0d34-0410-b5e6-96231b3b80d8
2013-01-05 00:42:50 +00:00
..
Host.inc
Memory.inc Go ahead and get rid of the old page size interface and convert all the 2012-12-31 23:31:56 +00:00
Mutex.inc
Path.inc The assumption that /proc/self/exe always exists is incorrect. 2012-09-26 08:30:35 +00:00
PathV2.inc Go ahead and get rid of the old page size interface and convert all the 2012-12-31 23:31:56 +00:00
Process.inc Eric thought that Darwin was right to use -1 consistently rather than 2013-01-05 00:42:50 +00:00
Program.inc Remove an unused method on Program. 2012-12-31 23:44:47 +00:00
README.txt
RWMutex.inc
Signals.inc Use the new script to sort the includes of every file under lib. 2012-12-03 16:50:05 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc
Unix.h Sort includes for all of the .h files under the 'lib' tree. These were 2012-12-04 07:12:27 +00:00

llvm/lib/Support/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.