Print this page
2nd round review feedback from rmustacc.

Split Close
Expand all
Collapse all
          --- old/usr/src/test/libc-tests/cfg/symbols/README
          +++ new/usr/src/test/libc-tests/cfg/symbols/README
↓ open down ↓ 19 lines elided ↑ open up ↑
  20   20  
  21   21  We have organized the files by header file, that is the tests for symbols
  22   22  declared in a header file (e.g. <unistd.h> appear in a file based on that
  23   23  header file's name (e.g. unistd_h.cfg.)  This is purely for convenience.
  24   24  
  25   25  Within these various declarations, we have the following field types:
  26   26  
  27   27  <envs>    This is a list of compilation environments where the symbol
  28   28            should be legal.  To indicate that the symbol must not be legal
  29   29            an environment group can be prefixed with "-".  For example,
  30      -          "SUS -SUSv4+" indicates a symbol that is legal in all SUS
       30 +          "SUS+ -SUSv4+" indicates a symbol that is legal in all SUS
  31   31            environments up to SUSv3, and was removed in SUSv4 and subsequent
  32   32            versions of SUS.  As you can see, we can list multiple environments
  33   33            or environment groups, and we can add or remove to previous groups
  34   34            with subsequent ones.
  35   35  
  36   36  <name>    This is a symbol name.  It follows the rules for C symbol names.
  37   37  
  38   38  <header>  This is a header file, for example, unistd.h.  Conventionally,
  39   39            the header files used should match the file where the test is
  40   40            declared.
↓ open down ↓ 32 lines elided ↑ open up ↑
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX