-
Notifications
You must be signed in to change notification settings - Fork 466
Implicit typing #484
New issue
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
Milestone
Comments
apparently, i made another mistake with implicit typing in one of my first PR's, i'll make a fix soon. |
Thanks @thijssteel ! I think using the flag |
Merged
weslleyspereira
added a commit
that referenced
this issue
Feb 12, 2021
Summary of PR #486: 1. There was a bug in the Makefile, and this is why AppVeyor stopped working. I solved it. 2. A recent commit was caused by a variable that was not defined, and the compiler couldn't track it. @thijssteel suggested adding `-fimplicit-none` to the CI on #484. I did it.
christoph-conrads
pushed a commit
to christoph-conrads/lapack
that referenced
this issue
May 23, 2021
…icit-none Summary of PR Reference-LAPACK#486: 1. There was a bug in the Makefile, and this is why AppVeyor stopped working. I solved it. 2. A recent commit was caused by a variable that was not defined, and the compiler couldn't track it. @thijssteel suggested adding `-fimplicit-none` to the CI on Reference-LAPACK#484. I did it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@weslleyspereira recently found a typo in a PR of mine, a typo that would have been impossible without implicit typing.
It would surprize me if any of the routines actually used implicit typing, so it probably always points to a bug.
I propose that we add
IMPLICIT NONE
to all the subroutines. Or perhaps add-fimplicit-none
to the CI.The text was updated successfully, but these errors were encountered: