You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A submodule has the same name either in a dependant library or in the same library but the module it is attached to have different names. The standard says
14.2.3 line 6: “… the submodule name by itself is not a local or global identifier.”
The fix to avoid this bug is easy: all submodule names are different (probably a best practise issue anyway).
Expected Behaviour
I always put the accessors for private data in a submodule with the name accessors_smod. They are attached to unique module names. FPM should not error and compile properly as the compilers will not balk at this.
Version of fpm
0.10.0, alpha
Platform and Architecture
linux
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Description
A submodule has the same name either in a dependant library or in the same library but the module it is attached to have different names. The standard says
14.2.3 line 6: “… the submodule name by itself is not a local or global identifier.”
The fix to avoid this bug is easy: all submodule names are different (probably a best practise issue anyway).
Expected Behaviour
I always put the accessors for private data in a submodule with the name accessors_smod. They are attached to unique module names. FPM should not error and compile properly as the compilers will not balk at this.
Version of fpm
0.10.0, alpha
Platform and Architecture
linux
Additional Information
No response
The text was updated successfully, but these errors were encountered: