errdp |
Table of contents
ProcedureERRDP ( Insert D.P. Number into Error Message Text ) SUBROUTINE ERRDP ( MARKER, DPNUM ) AbstractSubstitute a double precision number for the first occurrence of a marker found in the current long error message. Required_ReadingERROR KeywordsCONVERSION ERROR DeclarationsIMPLICIT NONE INCLUDE 'errhnd.inc' CHARACTER*(*) MARKER DOUBLE PRECISION DPNUM Brief_I/OVARIABLE I/O DESCRIPTION -------- --- -------------------------------------------------- MARKER I A substring of the error message to be replaced. DPNUM I The d.p. number to substitute for MARKER. Detailed_InputMARKER is a character string which marks a position in the long error message where a character string representing an double precision number is to be substituted. Leading and trailing blanks in MARKER are not significant. Case IS significant; 'XX' is considered to be a different marker from 'xx'. DPNUM is an double precision number whose character representation will be substituted for the first occurrence of MARKER in the long error message. This occurrence of the substring indicated by MARKER will be removed, and replaced by a character string, with no leading or trailing blanks, representing DPNUM. Detailed_OutputNone. ParametersLMSGLN is the maximum length of the long error message. See the include file errhnd.inc for the value of LMSGLN. Exceptions1) This routine does not detect any errors. However, this routine is part of the SPICELIB error handling mechanism. FilesNone. ParticularsThe effect of this routine is to update the current long error message. If no marker is found, (e.g., in the case that the long error message is blank), the routine has no effect. If multiple instances of the marker designated by MARKER are found, only the first one is replaced. If the character string resulting from the substitution exceeds the maximum length of the long error message, the characters on the right are lost. No error is signaled. This routine has no effect if changes to the long message are not allowed. ExamplesThe numerical results shown for this example may differ across platforms. The results depend on the SPICE kernels used as input, the compiler and supporting libraries, and the machine specific arithmetic implementation. 1) Create a user-defined error message, including both the short and long messages, providing the value of two double precision variables within the long message, and signal the error. Example code begins here. PROGRAM ERRDP_EX1 IMPLICIT NONE C C Set long error message, with two different MARKER C strings where the value of the double precision C variables will go. Our markers are '#' and 'XX'. C CALL SETMSG ( 'LONG MESSAGE. Invalid operation value. ' . // ' The value was #. Left endpoint ' . // 'exceeded right endpoint. The left ' . // 'endpoint was: XX. The right endpoint ' . // 'was: XX.' ) C C Insert a double precision where the # is now. C CALL ERRDP ( '#', 5.D0 ) C C Insert another double precision number in the long C message where the first XX is now. C CALL ERRDP ( 'XX', 73.4567D0 ) C C Signal the error. C CALL SIGERR ( 'SPICE(USERDEFINED)' ) END When this program was executed on a Mac/Intel/gfortran/64-bit platform, the output was: ============================================================*** Toolkit version: N0066 SPICE(USERDEFINED) -- LONG MESSAGE. Invalid operation value. The value was 5.0000000000000E+00. Left endpoint exceeded right endpoint. *** endpoint was: 7.3456700000000E+01. The right endpoint was: XX. Oh, by the way: The SPICELIB error handling actions are USER- TAILORABLE. You can choose whether the Toolkit aborts or co*** when errors occur, which error messages to output, and where*** the output. Please read the ERROR "Required Reading" file, *** the routines ERRACT, ERRDEV, and ERRPRT. ============================================================*** Warning: incomplete output. 6 lines extended past the right margin of the header and have been truncated. These lines are marked by "***" at the end of each line. Note that the execution of this program produces the error SPICE(USERDEFINED), which follows the NAIF standard as described in the ERROR required reading. Restrictions1) The caller must ensure that the message length, after sub- stitution is performed, doesn't exceed LMSGLN characters. Literature_ReferencesNone. Author_and_InstitutionN.J. Bachman (JPL) J. Diaz del Rio (ODC Space) B.V. Semenov (JPL) W.L. Taber (JPL) VersionSPICELIB Version 2.3.0, 13-AUG-2021 (JDR) Added IMPLICIT NONE statement. Edited the header to comply with NAIF standard. Removed unnecessary $Revisions section. Added complete code example based on existing fragments. SPICELIB Version 2.2.1, 08-JAN-2014 (BVS) Fixed header example (5.0 -> 5.D0). SPICELIB Version 2.2.0, 29-JUL-2005 (NJB) Bug fix: increased length of internal string DPSTRG to handle 3-digit exponents. SPICELIB Version 2.1.0, 29-JUL-1997 (NJB) Bug fix: extraneous leading blank has been removed from numeric string substituted for marker. Maximum length of the long error message is now represented by the parameter LMSGLN. Miscellaneous format changes to the header, code and in-line comments were made. SPICELIB Version 1.0.1, 10-MAR-1992 (WLT) Comment section for permuted index source lines was added following the header. SPICELIB Version 1.0.0, 31-JAN-1990 (NJB) |
Fri Dec 31 18:36:20 2021