.TH "xerbla_array" 3 "Wed Feb 7 2024 11:30:40" "Version 3.12.0" "LAPACK" \" -*- nroff -*- .ad l .nh .SH NAME xerbla_array \- xerbla_array: error reporting, callable from C .SH SYNOPSIS .br .PP .SS "Functions" .in +1c .ti -1c .RI "subroutine \fBxerbla_array\fP (srname_array, srname_len, info)" .br .RI "\fBXERBLA_ARRAY\fP " .in -1c .SH "Detailed Description" .PP .SH "Function Documentation" .PP .SS "subroutine xerbla_array (character(1), dimension(srname_len) srname_array, integer srname_len, integer info)" .PP \fBXERBLA_ARRAY\fP .PP \fBPurpose:\fP .RS 4 .PP .nf XERBLA_ARRAY assists other languages in calling XERBLA, the LAPACK and BLAS error handler\&. Rather than taking a Fortran string argument as the function's name, XERBLA_ARRAY takes an array of single characters along with the array's length\&. XERBLA_ARRAY then copies up to 32 characters of that array into a Fortran string and passes that to XERBLA\&. If called with a non-positive SRNAME_LEN, XERBLA_ARRAY will call XERBLA with a string of all blank characters\&. Say some macro or other device makes XERBLA_ARRAY available to C99 by a name lapack_xerbla and with a common Fortran calling convention\&. Then a C99 program could invoke XERBLA via: { int flen = strlen(__func__); lapack_xerbla(__func__, &flen, &info); } Providing XERBLA_ARRAY is not necessary for intercepting LAPACK errors\&. XERBLA_ARRAY calls XERBLA\&. .fi .PP .RE .PP \fBParameters\fP .RS 4 \fISRNAME_ARRAY\fP .PP .nf SRNAME_ARRAY is CHARACTER(1) array, dimension (SRNAME_LEN) The name of the routine which called XERBLA_ARRAY\&. .fi .PP .br \fISRNAME_LEN\fP .PP .nf SRNAME_LEN is INTEGER The length of the name in SRNAME_ARRAY\&. .fi .PP .br \fIINFO\fP .PP .nf INFO is INTEGER The position of the invalid parameter in the parameter list of the calling routine\&. .fi .PP .RE .PP \fBAuthor\fP .RS 4 Univ\&. of Tennessee .PP Univ\&. of California Berkeley .PP Univ\&. of Colorado Denver .PP NAG Ltd\&. .RE .PP .SH "Author" .PP Generated automatically by Doxygen for LAPACK from the source code\&.