Changeset 943 for trunk/doc/pslib/psLibSDRS.tex
- Timestamp:
- Jun 9, 2004, 6:05:58 AM (22 years ago)
- File:
-
- 1 edited
-
trunk/doc/pslib/psLibSDRS.tex (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/pslib/psLibSDRS.tex
r933 r943 1 %%% $Id: psLibSDRS.tex,v 1.5 3 2004-06-08 20:12:36 price Exp $1 %%% $Id: psLibSDRS.tex,v 1.54 2004-06-09 16:05:58 eugene Exp $ 2 2 \documentclass[panstarrs]{panstarrs} 3 3 … … 949 949 PSLib and any project needed to use PSLib must define the necessary 950 950 error codes and associated message strings. An array of error codes 951 may be registered with the PSLib error handler using a private 952 function: 951 may be registered with the PSLib error handler using the function: 953 952 \begin{verbatim} 954 953 void psErrorRegisterSet(const psErrorDescription *errors, int nerror); … … 962 961 \end{verbatim} 963 962 PSLib 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 error963 \code{psErrorRegisterSet}, which should be called as part of the 964 program initialization to set up the error codes. It is left to the 965 external project to produce their own error registration functions 966 which must also be called during initialization. There is a clear need 967 to coordinate the choice of error numbers. It is expected that error 969 968 code ranges for different projects must be managed by the Project 970 969 Office within Pan-STARRS.
Note:
See TracChangeset
for help on using the changeset viewer.
