llvm-6502/lib/System/Unix
Michael J. Spencer fae76d0734 This is the first step in adding sane error handling support to LLVMSystem.
The system API's will be shifted over to returning an error_code, and returning
other return values as out parameters to the function.

Code that needs to check error conditions will use the errc enum values which
are the same as the posix_errno defines (EBADF, E2BIG, etc...), and are
compatable with the error codes in WinError.h due to some magic in system_error.

An example would be:

if (error_code ec = KillEvil("Java")) { // error_code can be converted to bool.
  handle_error(ec);
}

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@119360 91177308-0d34-0410-b5e6-96231b3b80d8
2010-11-16 18:31:52 +00:00
..
Alarm.inc
Host.inc
Memory.inc
Mutex.inc
Path.inc Add method for checking if a path is a symbolic link. 2010-11-07 04:36:50 +00:00
Process.inc
Program.inc Make FindProgramByName return paths with slashes unmodified on Windows. 2010-11-02 20:32:39 +00:00
README.txt
RWMutex.inc
Signals.inc CrashRecovery: Fix raise() override to actually send the right signal, *cough*. 2010-10-08 18:31:34 +00:00
system_error.inc This is the first step in adding sane error handling support to LLVMSystem. 2010-11-16 18:31:52 +00:00
ThreadLocal.inc Add an erase() method to llvm::ThreadLocal. 2010-07-28 22:49:43 +00:00
TimeValue.inc
Unix.h

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.