NAG Library Routine Document

x10cj_a1w_f (callback_read_type_a1w)

1
Purpose

x10cj_a1w_f reads an object of the type nagad_a1w_w_rtype from a callback data object created by x10ba_a1w_f.

2
Specification

Fortran Interface
Subroutine x10cj_a1w_f ( cb_handle, xa, ifail)
Integer, Intent (Inout):: ifail
Type (c_ptr), Intent (Inout):: cb_handle
Type (nagad_a1w_w_rtype), Intent (Out):: xa
C++ Header Interface
#include <nagad.h>
extern "C" {
void  x10cj_a1w_f_ (void *&cb_handle, nagad_a1w_w_rtype &xa, Integer &ifail)
}
VBA (Long integers) Header Interface
Declare PtrSafe Sub X10CJF Lib "libname" ( _
    cb_handle As LongPtr, xa As nagad_a1w_w_rtype, ifail As Long)

3
Description

For routines where it is necessary to perform callback operations via one or more companion callbacks, data must be passed between the procedure argument and any such companion callback via a callback data object as created by x10ba_a1w_f. x10cj_a1w_f can be used to extract an object of the type nagad_a1w_w_rtype from the callback data object. In this way an object of the type nagad_a1w_w_rtype can be communicated between a procedure argument and its companion callbacks.
Note that writing to and reading from a callback data object must be performed in strict order without omission. Reading a data item from the object is equivalent to removing that item from a data stack; reading is therefore not passive, but updates the callback data object.

4
References

None.

5
Arguments

1:     cb_handle – Type (c_ptr)Input/Output
On entry: will contain a handle to the callback data object.
On exit: will contain a handle to the updated callback data object, with data item removed from data stack.
2:     xa – Type (nagad_a1w_w_rtype)Output
On exit: an object of the type nagad_a1w_w_rtype, xa, to be extracted from the callback data object.
3:     ifail – IntegerInput/Output
On entry: ifail must be set to 0, -1 or 1. If you are unfamiliar with this argument you should refer to Section 3.4 in How to Use the NAG Library and its Documentation for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value -1 or 1 is recommended. If the output of error messages is undesirable, then the value 1 is recommended. Otherwise, if you are not familiar with this argument, the recommended value is 0. When the value -1 or 1 is used it is essential to test the value of ifail on exit.
On exit: ifail=0 unless the routine detects an error or a warning has been flagged (see Section 6).

6
Error Indicators and Warnings

If on entry ifail=0 or -1, explanatory error messages are output on the current error message unit (as defined by x04aaf).
Errors or warnings detected by the routine:
ifail=1
On entry, cb_handle does not define a valid handle to a NAG AD callback data object. It has not been initialized or has been corrupted.
ifail=-99
An unexpected error has been triggered by this routine. Please contact NAG.
See Section 3.9 in How to Use the NAG Library and its Documentation for further information.
ifail=-399
Your licence key may have expired or may not have been installed correctly.
See Section 3.8 in How to Use the NAG Library and its Documentation for further information.
ifail=-999
Dynamic memory allocation failed.
See Section 3.7 in How to Use the NAG Library and its Documentation for further information.

7
Accuracy

Not applicable.

8
Parallelism and Performance

x10cj_a1w_f is not threaded in any implementation.

9
Further Comments

None.

10
Example

See examples for computational routines in the NAG AD Library, for example, Section 10 in c05ay_a1w_f.