Dan Williams

Thanks for sharing that. In general, I agree with what is proposed. The stuff about the dialects is probably overly complex. I tried again to reproduce this issue outside our...

@mwichmann Hi Mats, I ran into this as well but it's that it does not support `.f90` either. I worked around it like this: https://github.com/dnwillia-work/scons/commit/16e3cd2585a172ebd868d8bf8228c310beb0eadc but ideally I think what...

Personally I think the right thing to do is remove the `.i` based suffixes entirely. So you could delete the code from the Intel Fortran modules that is setting that...

> I have a more advanced version of this branch staged locally, that wraps all existing Python functionality and some additional features into a Python class. However the challenges I...

FWIW I always use a virtual environment locally in my source tree and install all the necessary Python packages for Modern Fortran into that. For instance, you could do this:...

Hey Matts and William! So I needed this one today.... The use case was that I'm redistributing some gcc/g++/gfortran libraries with my project and I would like to maintain these...

@aparnajyothi-y No problem. @RobPasMue suggested I try v4 as a workaround and I can confirm that this is working.

I agree this is a bit awkward. The MAPDL documentation for all the commands is quite extensive and it seems a bit awkward to have to manually reproduce the content...

Yeah I think this will be kind of a per-product strategy in terms of how to do it but I agree. Chatting with our documentation team the idea would just...