Skip to content
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

Rule requiring implicit none in interfaces is too strict #11

Open
LiamPattinson opened this issue Jan 29, 2024 · 0 comments
Open

Rule requiring implicit none in interfaces is too strict #11

LiamPattinson opened this issue Jan 29, 2024 · 0 comments

Comments

@LiamPattinson
Copy link
Collaborator

The reason interface blocks don't inherit the implicit none of their surrounding scope is that they're often used to create modular interfaces to old FORTRAN 77 code, and there's no way to tell in general which interface functions/subroutines refer to implicitly typed code and which refer to explicitly typed code.

A good candidate for where we should be asserting the use of implicit none in interface blocks is for bind(C) functions/subroutines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant