v3.0.0 - 14 Feb 2011
Bug Fixes
- Updated installer to
- Be compatible with R >=2.12.0 see issue 84 - as installation of RFortran is no longer backwards compatible with R <2.12.0 - this necessitated the increase to v3.0.0
- Be compatible with Windows 7 - users are now asked to provide an install path, instead of default C:\Program Files\RFortran (Windows 7/Vista does not easily allow writing to C:\Program Files\). This should also work for Windows Vista but has not been tested
- Several minor bug fixes - issue 85 , issue 83 , issue 80 , issue 79 , issue 74 , issue 70 , issue 71 .
New Features
- Several simple test programs are included in the installer (as suggested by issue 77 ). These can be used to test installation of RFortran - this is useful for all users - but especially those who are using programs (e.g. petit bateau) that depends on RFortran and do not have IVF/CVF
v2.1.2 - 21 June 2010
Download version here
Bug Fixes
- Minor updates to enhance interoperability of DMSL/RFortran
- Updated tutorial examples for consistency with final revised EMS paper
v2.1.1 - 20 May 2010
Download version here
Bug Fixes
- Minors fixes for CVF versions
v2.1.0 - 14 May 2010
Download version here
Bug Fixes
- Enhanced CVF compatibility ( issue 39 , issue 55 , issue 56 )
- Fixed error in handling of vartype in Rput_Rget ( issue 56 )
- Enhanced labelling of errors and warnings, including increased debug diagnostics in log file ( issue 60 )
- Improved programmatic assignment of RFortran setting for integration with DMSL/BATEA ( issue 62 )
- Performed full deprecation or Rput("command") routine ( issue 64 )
New Features
- Rcall function - provides an easy way to transfer multiple variables and execute multiple commands
v2.0.1 - 4 Mar 2010
Download version here
Bug Fixes
- Issue 41 , Issue 42 , Issue 43 : RFortran is almost fully F2003 compliant and project settings now warn for non-standard F2003.
- InvalidOption and typeOption optional arguments for Rget were not operational in v2.0.0 and have now been re-instated and updated
- Issue 44 : Changed arguments type of allmessages,
- Issue 38 : Updated core functionality of RFortran_DummyInterfaces.f90 to match this version
v2.0.0 - 19 Feb 2010
Download version here
Bug Fixes
New Features - Added function Reval to replace Rput(command)
- Added functionality for visible and invisible modes for Rgui, controlled by RGuiVisibleIn optional argument in Rinit
- Added STATUS optional argument for Rput, that controls whether variables can be overwritten
- Added rm optional argument for Rget, that removes variable from R after transfer to Fortran
- Massive improvement in efficiency for error handling for Rget
- More comprehensive error handling in RFortran
- ok values have a look-up table with description and remedy added to log file
- errors from R are returned to log file
- source code re-arrangement including use of include files to improve efficiency
- Changed user folder to ext folder for extended RFortran functionality
- Modified handling of Rscripts - now loaded on an as-needs basis, rather then all-at-once
- Updated tutorial examples for revised version of Intro RFortran paper
Known Bugs
- RFortran_CVF project files have yet to be updated for this version - this is aimed to occur in the next minor version release.
Backwards Compatibility
Potential backwards compatibility issues are:
- $error, $warn etc flags used in MUtilsLib_MessageLog (call message($error,"") ) have been replaced with log_error, log_warn etc because they were non standard Fortran.
- If you supply a scriptpath to Rinit, the large numbers of scripts trying to be loaded can produce errors. Better to remove this and load scripts on an as-needs basis.
v1.0.0 - June 2009
First open source version of RFortran
Download version here
Bug Fixes
- Eradicated all write(6,*) or write(*,*) statements in Rput/Rget
- Streamlined use of Rgraphics Device, several routines were doing similar tasks
New Features - Major update to RFortran Installer to automate all installation tasks
- Modern UI interface
- Install RFortran Components
- Auto-detects install folder of current version of RGui
- Updates RFortran.settings with Rgui installer folder
- Downloads R packages for core and enhanced functionality from internet
- Produces Start Menu Items
- Produces RFortran Uninstaller
- Can be used to update RFortran installation when a new version of R is installed
- Major rearrangement/tidy up of source code/project files, to make it easier to understand and use
- Introduction of RFortran settings file to handle user modifiable settings, see RFortran Settings
- Major update to Rinit - several additional optional arguments to control how RFortran runs - see Rinit
- Streamlined handling of R Graphics Devices
- Launch of RFortran web/google code site
- Home Page
- Source code version control
- Issue Tracker to manage bug requests/feature enhancements etc
- Wiki - provides major source of information for RFortran users (Download and Installation, FAQ, HowtoUse etc)
- Utilities now seperated out into its own independent project, see MUtilsLib. RFortran installer handles downloading of updates to this utilities libray
- Ability to retrieve messages from log file
- Added tutorial examples
- Submitted Introduction to RFortran paper
Backwards Compatibility
- As this release is a major rearrangement of the source code many old routines have been deprecated. In most cases, the old routine interface has been retained and reports a warning that this routine has been deprecated and what to replace it with.
- If you have any problems please report an issue during beta testing
- This maintains backwards compatibility, except for:
- Utilities
- Previously utilities (message logging, string funcs etc) were integrated as part of the RFortran library, ie. if you use RFortran you would also get access to the message logging routines
- As utilities is now a independent library MUtilsLib it is no longer integrated as part of RFortan
- You will need to add Use MUtilsLib to your code if you use any MUtilsLib routines, e.g. call message(... or operator(//) to provide access to these routines
Requirements
- R (>=2.9.0) - due to changes in requirements for RCOM
- IVF (>=11.0) - to view projects/solutions, due to changes in *.vfproj file format
v0.950 - 27 November 2008
- Rearrangement of RFortran File Structure
- Beta version with installer released to GK and DK - readme still needs updating
v0.940 - 22nd April 2008
- Added support for error checking of type mismatches when using Rget
- Modified auto-opening of R to enhance installation, Path to RGui.exe, RGuiPath is now a global variable that needs to be set by the user. Previously, this auto-opening relied on the path to RGUI.exe being set in PATH environment variable during installation which required administrator rights. This modification means this requirement has now been removed.
v0.922 - 21st January 2008
- Added support for using RFortran with Fortran Windows Applications (with thanks to Dimitri Kavetski)
- Changed fatal errors to recoverable warnings to prevent stopping heavy computations in calling routine due to inability to use R/RFortran
- Removed all write(*,*) and pause statements
- Improved error handling of call COMCREATEOBJECTBYGUID in Rinit
- Rinit now returns a error msg if R is not initial used properly
- Beta version of support for RFortran to manage multiple graphics devices (handy if several programs are running RFortran simultaneously)
- Added RFortran_OutputDeviceHandling.f90 with additional interface to Rinit which is called if outputtype is specified
v0.910 - 24th September 2007
- Minor updates and tidy up to readme file and ability to read scriptpaths with spaces in filenames
v0.909 - 8th August 2007
Minor Updates and Bug Fixes
- Rinit now has ability to autostart R during debugging
- Fixed bug 20 - Rget now works in IVF v9.1 and higher
- Added more Rplot routines including
- Rfilledcontour
- Rcolpersp3d
- RplotProblimSeries
- Reorganised TEST_*.f90 files into seperate source code to make it easier to understand
- Added RFortran Quickstart Guide
v0.903 - 7th March 2007
- First General Release of RFortran Suite
Version Numbering
As of v1.0.0 (June 2009) following version numbering system is adopted
Version Number: vX.Y.Z
- Z = micro number - changes to micro number are bug fixes only, or small enhancements to existing features. No new features. They are both forward- and backward- compatible
- Y = minor number - changes to minor number may introduce new features, but not too many. They are backwards compatible, but not forward-compatible
- X = major number - changes to major number mark compatibility boundaries. A new major version can be forward- and backward-incompatible. A major version release is expected to have new features, and may even have entire new feature sets.
For further information refer to section on Simple Strategy in Karl's Fogels book, Producing Open Source Software,
A major or minor version release, accompanied by a new installer, is planned for every 3-6 months.
Micro version releases, accompanied by a new installer, will only appear to correct a major bug.
Updates to source code to correct minor bug fixes, minor ehancements etc. can checked out from the source code repository