We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
const
[in]
See lapack.h for an example already in use, for example
lapack.h
#define LAPACK_dgetrf LAPACK_GLOBAL(dgetrf,DGETRF) void LAPACK_dgetrf( lapack_int const* m, lapack_int const* n, double* A, lapack_int const* lda, lapack_int* ipiv, lapack_int* info );
has marked m, n and lda constant which matches the [in] arguments from the docs
m
n
lda
I went with the macro-less
extern void dgetrf_(const int* M, const int* N, double* A, const int* LDA, int* IPIV, int* INFO);
in a blog post about LAPACK.
The text was updated successfully, but these errors were encountered:
In
As some other prior art, the Intel MKL docs on their LAPACK interface says
The arguments of the C interfaces for the Intel MKL LAPACK functions comply with the following rules: Scalar input arguments are passed by value. Array arguments are passed by reference. Array input arguments are declared with the const modifier. ...
The arguments of the C interfaces for the Intel MKL LAPACK functions comply with the following rules:
...
Sorry, something went wrong.
Use const pointers for arguments of type [in] headers. (#169)
76d7c1b
Fixes #168.
dhermes
Successfully merging a pull request may close this issue.
See
lapack.h
for an example already in use, for examplehas marked
m
,n
andlda
constant which matches the[in]
arguments from the docsI went with the macro-less
in a blog post about LAPACK.
The text was updated successfully, but these errors were encountered: