IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jun 9, 2004, 6:05:58 AM (22 years ago)
Author:
eugene
Message:

SDRS changes to psError wording
SRS changes: shall to must

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/pslib/psLibSDRS.tex

    r933 r943  
    1 %%% $Id: psLibSDRS.tex,v 1.53 2004-06-08 20:12:36 price Exp $
     1%%% $Id: psLibSDRS.tex,v 1.54 2004-06-09 16:05:58 eugene Exp $
    22\documentclass[panstarrs]{panstarrs}
    33
     
    949949PSLib and any project needed to use PSLib must define the necessary
    950950error codes and associated message strings.  An array of error codes
    951 may be registered with the PSLib error handler using a private
    952 function:
     951may be registered with the PSLib error handler using the function:
    953952\begin{verbatim}
    954953void psErrorRegisterSet(const psErrorDescription *errors, int nerror);
     
    962961\end{verbatim}
    963962PSLib internal errors must be registered with the function
    964 psErrorRegister, which should be called as part of the program
    965 initialization to set up the error codes.  It is left to the external
    966 project to produce their own error registration functions which must
    967 also be called during initialization. There is a clear need to
    968 coordinate the choice of error numbers.  It is expected that error
     963\code{psErrorRegisterSet}, which should be called as part of the
     964program initialization to set up the error codes.  It is left to the
     965external project to produce their own error registration functions
     966which must also be called during initialization. There is a clear need
     967to coordinate the choice of error numbers.  It is expected that error
    969968code ranges for different projects must be managed by the Project
    970969Office within Pan-STARRS.
Note: See TracChangeset for help on using the changeset viewer.