Could you, please, consider having just 2 fortran modules: fruit.f90 and fruit_mpi.f90 instead of 3? I would rather like to see fruit_util.f90 absorbed into fruit. fruit_mpi.f90 needs both of them anyway? Or are there some deep thoughts against this?
I would also like to see from you some questionnaire about the usefulness of the ruby gui etc for fortran developers before making so much efforts towards this? Because I still have some doubts about combination of ruby and fortran. Yes, I dont use ruby and this part of functionality of fruit:)
But thanks anyway for the new version!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you, please, consider having just 2 fortran modules: fruit.f90 and fruit_mpi.f90 instead of 3? I would rather like to see fruit_util.f90 absorbed into fruit. fruit_mpi.f90 needs both of them anyway? Or are there some deep thoughts against this?
I would also like to see from you some questionnaire about the usefulness of the ruby gui etc for fortran developers before making so much efforts towards this? Because I still have some doubts about combination of ruby and fortran. Yes, I dont use ruby and this part of functionality of fruit:)
But thanks anyway for the new version!
Great to know that I'm not the only user of FRUIT. Thank you.
In FRUIT 3.3.9, new fruit.f90 includes both former fruit.f90 and fruit_util.f90.
On rake (ruby) part of FRUIT, I'm using it.
With Jenkins, it runs whole unit tests (regression test) even when I'm taking nap.
Great! Thanks for the new version and for the answers.