llvm-mirror/lib/System/Unix
Dan Gohman e2ee41d1d1 Don't use plain %x to print pointer values. I had changed it from %p
since %p isn't formatted consistently, but obviously plain %x is wrong.
PRIxPTR with a cast to uintptr_t would work here, but that requires
inconvenient build-system changes. %lu works on all current and
foreseable future hosts.

llvm-svn: 60616
2008-12-05 23:39:24 +00:00
..
Alarm.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
Host.inc Add llvm::sys::{osName,osVersion} for retrieving operating system name 2008-10-02 01:17:28 +00:00
Memory.inc Update the stub and callback code to handle lazy compilation. The stub 2008-10-20 21:39:23 +00:00
Mutex.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
Path.inc add a helper method to sys::Path for clang, patch by 2008-08-11 23:39:47 +00:00
Process.inc Restore code to disable crash catcher on older OS X systems 2008-04-12 00:47:46 +00:00
Program.inc Fix redirection of stderr in sys::Program::ExecuteAndWait. There was logic 2008-06-12 12:53:35 +00:00
README.txt
Signals.inc Don't use plain %x to print pointer values. I had changed it from %p 2008-12-05 23:39:24 +00:00
TimeValue.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
Unix.h Clean up the use of static and anonymous namespaces. This turned up 2008-05-13 00:00:25 +00:00

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.