Brad Richardson
Brad Richardson
So, the idea here is that, not only should FPM be able to use "non"-FPM packages, it should also be able to *generate* "non"-FPM packages? I think this may be...
Ok, let's at least finish a beta version that just supports standard FPM projects before we start tackling this one though.
@certik , this is the paper I was showing earlier today. I tried to simplify the example just a bit to hopefully make it easier to grok.
I would lean towards option 1 as being easier to implement in fpm. It just doesn't fetch and build optional dependencies unless specified, and only defines the environment variables for...
Based on reading of the standard, it looks like the path forward here has to do with separate procedures for different types, and to use select rank internally to dispatch...
Taking a fresh look at this, I don't think it's a problem. > A Fortran procedure interface is interoperable with a C function prototype if > ... > (5) any...
I *think* the tests that are failing are due to the line `result_ = assert_that(all(scramlet == co_max_scramlet),"all(scramlet == co_max_scramlet)")`, which should use `expected_scramlet` instead. It may be worth adding 1,...