search

hodgesse1 / rfortran

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

Improved handling of COM open/close from RFortran #48

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
*** Please provide a description of the enhancement you are requesting.

Check if COM server is already open before attempting to initialise it
during Rinit.

Similarly, do not close the COM server when executing Rclose.

This is essential because modern programming may require concurrent use of
multiple COM clients. The current code mangles this, leading to error
messages, etc.

Implementing this requires defining a global variable that tracks the
status of the COM server (see attached file for a partial implementation).

The opening and closing of COM servers should be done separately. See DMSL
module xsystem for an initial implementation.

Original issue reported on code.google.com by dmitri.k...@gmail.com on 14 Sep 2009 at 1:35

Attachments:

GoogleCodeExporter commented 8 years ago 
D,

I agree a global variable (outside RFortran) that tracks COM status is 
important for 
managing multiple COM clients.

Not sure whether filepaths_dmsl_kit.f90 is the most appropriate place for it. 
In the current implementation, I would need add filepaths_dmsl_kit to 
Mutilslib_miniDMSL.f90 to enable the stand-alone version of RFortran to run. 
This will likely lead to confusion for Rfortran users because of the DMSL 
filepaths 
that exist in filepaths_dmsl_kit.f90 that are not used at all by RFortran and 
have 
alternatives that are used by RFortran.

I suggest that openedCOM be placed in kinds_dmsl_kit.f90 (along with with the 
other 
DMSL global variables)

Mark

Original comment by mark.th...@gmail.com on 11 Feb 2010 at 10:02

GoogleCodeExporter commented 8 years ago 
Fixed in version 2.0.0

Original comment by mark.th...@gmail.com on 19 Feb 2010 at 5:26