search

hodgesse1 / rfortran

Automatically exported from code.google.com/p/rfortran
0 stars 0 forks source link

poor distinction between "error" and "warning" #60

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
*** What steps will reproduce the problem?

Run any tutorial example

*** What is the expected output?

Clear indications of whether the test succeeded

*** What do you see instead?

Some error messages that apparently should be ignored (eg, 

-----------
Error: Reached end of file before finding keyword:[RGuiVisible] in settings
file:C:\DMITRI\My_Documents\FortranLibs\RFortran\settings\RFortran.set
Error: Error finding keyword:[RGuiVisible] in settings
file:C:\DMITRI\My_Documents\FortranLibs\RFortran\settings\RFortran.set
Comment: RFortran is auto-opening R, and will wait 30.0000000000000 secs for R
to initialise. To change wait time set wait4RDef in RFortran.set file OR
set dummy argument wait4RIn when calling Rinit
-----------

It is not obvious if/when such error messages should be ignored. When
genuine errors appear to occur (eg, issue 59), it is hard to figure out if
there is an error.

*** What version of RFortran are you using?

2.0

*** Please provide any additional information below.

It seems many of the current "error messages" should become "warnings". I
think this is a fairly important point both for potential new users, and
for existing users diagnosing potential problems and testing new versions.

Original issue reported on code.google.com by dmitri.k...@gmail.com on 10 Apr 2010 at 3:44

GoogleCodeExporter commented 8 years ago

Original comment by mark.th...@gmail.com on 10 Apr 2010 at 4:19

GoogleCodeExporter commented 8 years ago

Original comment by mark.th...@gmail.com on 16 Apr 2010 at 6:07