aboutsummaryrefslogtreecommitdiff
path: root/SRC/zgesvxx.f
diff options
context:
space:
mode:
authorjulie <julielangou@users.noreply.github.com>2012-04-23 21:33:19 +0000
committerjulie <julielangou@users.noreply.github.com>2012-04-23 21:33:19 +0000
commit99af1a44a9e87a4a1b0b11d343835a79a52b0697 (patch)
tree0e350c4a23f4b6c4c978286b72b4bb6d47ab6713 /SRC/zgesvxx.f
parentf5ad5058f76df5d4cfcb67cb76a3902770b71a32 (diff)
Fix problems in comments found by Alexander Kobotov
Just taking a quick look on the new release I noticed some minor issues there, which probably caused by a generation script: - If you explore diff for files (c/z)gbrfsx, cgbsvx, cgbsvxx, cheequb, clanhf, zheequb you could find that number of datatype descriptions in documentation were changed to incorrect one (DOUBLE PRECISION instead of COMPLEX, or COMPLEX*16 instead of just COMPLEX). + cunbdb has CMPLX instead of COMPLEX for X12 parameter. + zggevx RWORK become REAL instead of correct DOUBLE PRECISION - Number of files got following string "/ output)", which seems meaningless. Just grep for it.
Diffstat (limited to 'SRC/zgesvxx.f')
-rw-r--r--SRC/zgesvxx.f2
1 files changed, 1 insertions, 1 deletions
diff --git a/SRC/zgesvxx.f b/SRC/zgesvxx.f
index 29ab7e74..3ac901f6 100644
--- a/SRC/zgesvxx.f
+++ b/SRC/zgesvxx.f
@@ -453,7 +453,7 @@
*>
*> \param[in,out] PARAMS
*> \verbatim
-*> PARAMS is / output) DOUBLE PRECISION array, dimension NPARAMS
+*> PARAMS is DOUBLE PRECISION array, dimension NPARAMS
*> Specifies algorithm parameters. If an entry is .LT. 0.0, then
*> that entry will be filled with default value used for that
*> parameter. Only positions up to NPARAMS are accessed; defaults