Le 17/03/2011 09:23, Daniel Harenberg a écrit :
Hi Michel,
as we found out, creating and switching build configurations
should work with the next (minor?) update of Photran.
Once that works, you could simply save your settings to your
debug config, or create a second with even stronger debug flags
(at least for the Intel Fortran Compiler
there are many more debug options). Since everybody probably has
different debug preferences, that should be the way to go,
instead of having
all kinds of flags enabled by default ... do you agree?
Hi Daniel,
I am afraid I do not agree. The reason is that for me the managed
make projects are very good for teaching and for testing an idea
fast, without bothering with Makefile (by the way, I have had
-fbounds-check in my Makefiles for a long time).
As soon as the project grows, for my research, I tend to prefer
using Makefile projects (but I test from time to time what it gives
with managed projects).
Hence, my request was more thinking to my students than to me: if I
want them to adopt eclipse instead of other Visual tools under
windows, it has to avoid them reading documentation. They are used
to point and click software and most do not know what a command line
interface is. Generally, they learn how to use a software by just
going through the menus and testing the things that sound good.
All that to say that, IMHO, the debug configuration should do just
what it means and offer all the possibilities to track and catch the
bugs by enabling by default the most conservative flags.
However, you are right that I could store my customized config and
distribute it to the students at the beginning of the first lab
session, but that is not so convenient since we are always short on
time.
--
sincerely_yours.txt
Sincerely yours,
Michel DEVEL
|