Hello everyone!
As you may be aware I have been accepted in this year’s GSoC under the mentorship of @hkvzjal and @fxm.
I will be giving weekly updates in this thread with it’s relevant PR’s, discussions etc
The initial plan is to start with implementing some path functions useful for further functionality taking inspiration from stdlib_os’s os_path module developed by @MarDie, @Arjen and @awvwgk and from how other languages like Python, Go, Rust etc handle it.
If you have any feedback, suggestions, questions etc do let me know!
Thank you!
Thanks for starting this, @suprit05. I’m tagging @FedericoPerini here as another mentor, who - alongside Jose - has a much deeper understanding of stdlib itself.
. I listed mine in probable order of relevance, but just guessing. There are others perhaps others can list. Some interesting differences in OOP versus procedural, how different platforms are distinguished, how proprocessing is applied, whether ford or doxygen is used, documentation approaches in general, …
If you plan to include support for files and directories you may also want to have a look at what @interkosmos did with fortran-unix and in particular the binding to dirent.
It is not portable to Windows but you can make it so with that dirent.h header.
Just some food for thoughts for your path functionality. When working with Nuke (in C#) I came across their AbsolutePath (resp. RelativePath) object which I found very convenient. In brief, it overloads the / operator so that you can build paths in a very visual way (e.g. newpath = root / folder / filename) and the operator takes care of choosing / or \ depending on the os and does the proper file concatenation.
. I listed mine in probable order of relevance, but just guessing. There are others perhaps others can list. Some interesting differences in OOP versus procedural, how different platforms are distinguished, how proprocessing is applied, whether ford or doxygen is used, documentation approaches in general, …