Closed GoogleCodeExporter closed 9 years ago
Original comment by dmitri.k...@gmail.com
on 10 Apr 2010 at 3:18
sample patch attached that uses relative paths to ensure the tutes are
associated
with their own version of RFortran (rather than an arbitrary existing version)
Original comment by dmitri.k...@gmail.com
on 10 Apr 2010 at 3:50
Attachments:
RE: use of $RFORTRAN_PATH variable in tutorial examples.
I understand your concerns re potentially difficult to diagnose problems.
However, I
prefer to continue their use because...
(1) The tutorial examples are designed for users to act like a template that
they can
copy and learn from. When using RFortran in their own code the relative paths
will
not work, whereas $RFORTRAN_PATH will
(2) Majority of users will have a single version of RFORTRAN- only the
developers are
likely to have multiple versions
(3) On my computer, (as I would recommend for developers) I have set-up two
additional environment variables: RFORTRAN_REL_PATH AND RFORTRAN_DEVEL_PATH and
in
the set-up folder I have batch files which sets RFORTRAN_PATH to
RFORTRAN_REL_PATH or
RFORTRAN_DEVEL_PATH depending on which version I am working on.
I understand this a bit of overhead for developers...but the simplicity and
convenience of using $RFORTRAN_PATH for users, outweighs this minor
inconvenience.
Furthermore I think the suggestion of reporting the RFORTRAN_PATH to the log
file is
an excellent one and has been implemented. As well as several other settings to
improve transparency.
Original comment by mark.th...@gmail.com
on 10 Apr 2010 at 4:22
Original issue reported on code.google.com by
dmitri.k...@gmail.com
on 10 Apr 2010 at 3:17