Skip to content

Conversation

@warrickball
Copy link
Contributor

This is the continuation of @VincentVanlaer's PR #696 (thanks Vincent!), which already made num/test comply with the Fortran 2008 standard. The rest of num is now compiled with a Fortran 2008 flag so the aim is to reduce the number of warnings before merging this into main.

We should make sure we can still build with ifort before merging.

@pmocz pmocz self-assigned this Aug 5, 2024
@pmocz pmocz changed the title Draft: Make num comply (mostly) with Fortran 2008 standard Make num comply (mostly) with Fortran 2008 standard Aug 7, 2024
@pmocz pmocz added the bug Something isn't working label Aug 7, 2024
@pmocz pmocz requested review from Debraheem and fxt44 as code owners August 8, 2024 14:27
@pmocz
Copy link
Member

pmocz commented Aug 12, 2024

Are we good to merge this?

@warrickball
Copy link
Contributor Author

I think so? I'm not sure if we want to wait until after the release. I personally don't mind but wouldn't mind at least another dev chipping in.

@pmocz
Copy link
Member

pmocz commented Aug 12, 2024

I think so? I'm not sure if we want to wait until after the release. I personally don't mind but wouldn't mind at least another dev chipping in.

Probably best to merge this in right after release actually, since we'd like to get the release out very soon and even though we tested this branch it doesn't add too much to users (yet, without the other successive PRs which should be left for after the release)

@pmocz pmocz mentioned this pull request Aug 13, 2024
@pmocz pmocz removed the bug Something isn't working label Aug 13, 2024
@pmocz
Copy link
Member

pmocz commented Aug 20, 2024

Merging now that we already have the 24.08.1 release branch

@pmocz pmocz merged commit e8b1fee into main Aug 20, 2024
@VincentVanlaer VincentVanlaer deleted the vv/num-test-standard branch April 17, 2025 08:11
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

Successfully merging this pull request may close these issues.

4 participants