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
I'll just throw this out as an alternative to building stdlib from scratch. Seth Johnson at ORNL has a project that can generate SWIG bindings to the C++ STL for Fortran. (see https://github.com/swig-fortran). I ran across his project a few months back and thought it interesting but didn't do a deep dive into what issues where involved in using it for things like lists etc. More info in the following two PDFS Johnson_Automated_Fortran-C++_Bindings_ArXiv.pdf siam-cse-johnsonsr.pdf
The text was updated successfully, but these errors were encountered:
STL can help with the containers and algorithms part of stdlib. I don't think it would help with any of the current functionality in our current master, would it? Or with the mathematics part.
See the README for the intended scope of stdlib.
Also if the C++ dependency could be only optional would be also helpful to lots of future users of stdlib.
Actually, I personnaly prefer a "pure" Fortran implementation if possible. I just put this forward as something that could be an option to provide some of the containers etc. needed for ADTs etc. if there is no consensus as to the best way to do it in Fortran. I agree it should only be an option (and only if its impracticle or time-consuming to do it in Fortran).
I'll just throw this out as an alternative to building stdlib from scratch. Seth Johnson at ORNL has a project that can generate SWIG bindings to the C++ STL for Fortran. (see https://github.com/swig-fortran). I ran across his project a few months back and thought it interesting but didn't do a deep dive into what issues where involved in using it for things like lists etc. More info in the following two PDFS
Johnson_Automated_Fortran-C++_Bindings_ArXiv.pdf
siam-cse-johnsonsr.pdf
The text was updated successfully, but these errors were encountered: