>Hi Rooters,
> when runnning relatively long interactive analysis jobs I noticed
>that the execution is affected by the changes I make to the source file
>of the running macro in case I save the changed macro on disk.
>Most of the times my job just crashes. Is there a good reason for CINT
>(ROOTCINT) following what is happening on disk *AFTER* the macro has been
>loaded and (fortunately) precompiled?
>
>If there is, it would be very nice if this feature which seems to be quite
>important were documented.
> regards, pasha.
In order to reduce memory consumption, cint reads source code from the file
system "on-the-fly". So, unless I/O library buffers the file contents, changin
g
a running macro affects the execution.
I agree this must be documented.
Masaharu Goto