llvm-6502/lib/Support/Unix
David Blaikie 58604cd944 Change default error_code ctor to a 'named ctor' so it's more self-documenting.
Unify default construction of error_code uses on this idiom so that users don't
feel compelled to make static globals for naming convenience. (unfortunately I
couldn't make the original ctor private as some APIs don't return their result,
instead using an out parameter (that makes sense to default construct) - which
is a bit of a pity. I did, however, find/fix some cases of unnecessary default
construction of error_code before I hit the unfixable cases)

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@150197 91177308-0d34-0410-b5e6-96231b3b80d8
2012-02-09 19:24:12 +00:00
..
Host.inc revert r147542 after comments from Joerg Sonnenberger 2012-01-05 18:28:46 +00:00
Memory.inc
Mutex.inc
Path.inc Remove a couple unused methods. PR11201. 2011-11-01 05:11:01 +00:00
PathV2.inc Change default error_code ctor to a 'named ctor' so it's more self-documenting. 2012-02-09 19:24:12 +00:00
Process.inc Remove SetWorkingDirectory from the Process interface. Nothing in LLVM 2012-01-15 08:41:35 +00:00
Program.inc Support/Program: Make Change<stream>ToBinary return error_code. 2011-12-13 23:16:49 +00:00
README.txt
RWMutex.inc
Signals.inc Disable the crash reporter when running lit tests. 2012-01-11 20:53:25 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc
Unix.h

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.