Brad Richardson
Brad Richardson
> * What coding style should I follow? I see fpm does not use many object-oriented facilities, most likely for compiler compatibility. Would having a `module_t` type, that extends the...
That's an interesting idea, but I think it may just move the ambiguity problem into fpm, not necessarily solve it. In order to achieve this, first, you'll need fpm to...
Thanks for putting this together. It will be invaluable as we try to support more compilers.
I just wanted to +1 this in hopes of eventual resolution. I'm trying to make use of it in an open source journal publication workflow: https://github.com/fortran-lang/fortran-forum-article-template
If I recall, the initial implementation wasn't pre-building them, but maybe I'm mistaken. This might be worth considering.
I like option 2. And if anyone **really** wants their package to have a conflicting name in the future, they can stand up their own registry and have their users...
That sounds well thought out and reasonable. I like it.
I've generally just resorted to using a string type for everything, and then for `intent(in)` arguments just using an interface to allow people to also pass in character literals (or...
I have a suggestion on how we should work through defining a style guide. Lot's of people are going to have very strong opinions on the subject, and on each...
> Does any current compiler actually implement this semantic? NAG supports it, but that may actually be it. I don't expect this to be a trivial problem to solve, but...