Re: CINT not releasing lock on #include'd file

From: Philippe Canal <pcanal_at_fnal.gov>
Date: Thu, 18 Mar 2010 16:25:44 -0500


Hi,

When CINT is working on a file it keeps it open so that it can refer to it if you access any of the not yet bytecode compiled function.

To edit the file you will need to explicitly unload it (via the CINT command .U).

Cheers,
Philippe.

On 3/18/10 2:09 PM, manday_at_gmx.net wrote:
> This is V 5.26 from VC++ 7.1 binary Windows MSI installer under Windows 7
>
> I'd like to know whether this is either my fault or indeed intended
> behaviour, if so, I'd like to know how to change it.
>
> ROOT/CINT, if asked to #include a source file aquires a file lock
> which it will not release, even after all operations have finished.
> This makes it hard to develop because I ultimately have to shut down
> the whole program in order to make changes to the included file. Is
> there any more flexible way that could enable me to include, edit,
> save and possibly even reinclude and reevaluate an external source file?
>
> Thank you. --MD
>
Received on Thu Mar 18 2010 - 22:25:53 CET

This archive was generated by hypermail 2.2.0 : Sat Mar 20 2010 - 23:50:01 CET