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

[build] Nonportable usage in fpm-0.10.1.F90 #1031

Closed
klausler opened this issue May 1, 2024 · 2 comments
Closed

[build] Nonportable usage in fpm-0.10.1.F90 #1031

klausler opened this issue May 1, 2024 · 2 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@klausler
Copy link

klausler commented May 1, 2024

Description

In fpm-0.10.1.F90 there are some instances of nonportable non-conforming Fortran usage.

  • At 27433, type(toml_error), allocatable :: toml_error uses the name of a derived type in the host scope to declare a variable of the same name in the local scope.

  • At 28256 and many sites after, the code attempts to define DEFERRED procedure bindings, but they are PRIVATE to their original module. It is valid to override a PRIVATE binding in another module (although many compilers fail to prevent the override from affecting usage in the original module), but not in the case of a DEFERRED binding.

Expected Behaviour

Compilation by most Fortran compilers

Version of fpm

fpm-0.10.1

Platform and Architecture

n/a

Additional Information

No response

@klausler klausler added the bug Something isn't working label May 1, 2024
@perazz perazz added the duplicate This issue or pull request already exists label May 1, 2024
@perazz
Copy link
Contributor

perazz commented May 1, 2024

Duplicate of #1012, these issues have been solved in #1011 #1013 and will appear in the next release. Thanks for pointing these out.

@perazz
Copy link
Contributor

perazz commented May 2, 2024

Will close this for now - please reopen if new issue arise, thank you.

@perazz perazz closed this as completed May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants