hodgesse1 / rfortran

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

Outdated CVF LIB project for RFortran? #55

Closed GoogleCodeExporter closed 8 years ago

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

Attempt to compile RFortran on Compaq Visual Fortran

*** What is the expected output? What do you see instead?

Expect to see compiled product. Instead I see compilation errors

*** What version of RFortran are you using?

Latest official release, "v2.0.0 XX February 2010" in the readme file

*** On which Windows operating system?

*** What Fortran compiler (name and version number) are you using?

*** What version of R are you using?

*** Please provide any additional information below.

RFortran website and submitted publication claims support for CVF.
Currently this appears buggy. Users like myself and BoM staff unable to use
RFortran under these circumstances ..

Original issue reported on code.google.com by dmitri.k...@gmail.com on 10 Mar 2010 at 10:07

GoogleCodeExporter commented 8 years ago
D,

If you read the release notes: 

http://code.google.com/p/rfortran/wiki/VersionHistory#v2.0.0_-_19_Feb_2010

You will note that the CVF version has yet to be updated for this v2.0.0 
release.
(mostly because my installation of CVF is currently inoperable requires 
re-installing)

You are most welcome to update the CVF files yourself.

Otherwise, this is planned to be updated in next minor release (v2.1) of 
RFortran.

Michael, are you able to update CVF at all?

Cheers,
Mark

Original comment by mark.th...@gmail.com on 10 Mar 2010 at 11:21

GoogleCodeExporter commented 8 years ago
CVF patch attached that appears to resolve CVF issues encountered thus far.

Includes both updates to the CVF project and also the buggy 'vartyp' handling.

May I ask Mark as Developer-In-Chief to check the changes (using IVF, as the
RGet_Rput file has changed) and update both the offical and trunk versions of 
RFortran.

d

Original comment by dmitri.k...@gmail.com on 10 Mar 2010 at 1:13

Attachments:

GoogleCodeExporter commented 8 years ago
D,

My CVF installation has somehow been corrupted on both my laptop and my desktop 
and I can no longer "add files". This means I can only do very limited testing 
of the CVF version. Do you know how I can 
un-install CVF- I could not find it in "add/remove programs"?

I've included most of your patches and also made some other changes to enable 
compilation with CVF. These have been committed to the release branch: 
svn/branches/ver-2.0 .

Would you mind updating and checking everything is working ok with your CVF 
before I create a new installer. 

One question - why the need to change the declaration of the variable, vartyp? 
Your patch changed it in some sections and not others. I would like to 
understand before I implement these changes in the 
entire code. The renaming of variables when used from a module is a F90 
feature. At my end, both CVF and IVF compile using the existing version. What 
bug did this create?

Once these minor issues are resolved I will create a new installer.

Mark 

You patch only changed it 

Original comment by mark.th...@gmail.com on 9 Apr 2010 at 1:38

GoogleCodeExporter commented 8 years ago
in the patched locations, you were accessing the same entity - which is 
incidentally,
a parameter (eg, VT_R8) in 2 ways: once via its original name and another thru 
the
renaming facility. this was triggering an error in my CVF 6.6.B (from memory, an
attempt to reference the same entity via different names). I also dont believe 
that
is allowed by the standard.

also I think the patch makes it clearer what is going on - it actually took me a
while to figure out what you were doing in the original code..

i have no problem checking the CVF version of RFortran.

Original comment by dmitri.k...@gmail.com on 9 Apr 2010 at 5:12

GoogleCodeExporter commented 8 years ago
I've updated the handling of vartyp, its available from the release version:

svn/branches/ver-2.0 

If could please check this in CVF and then I can close this ticket

Mark

Original comment by mark.th...@gmail.com on 10 Apr 2010 at 12:35

GoogleCodeExporter commented 8 years ago

Original comment by mark.th...@gmail.com on 11 Apr 2010 at 2:03

GoogleCodeExporter commented 8 years ago

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