Pasha and Richard,
>I'd suggest the following strategy of reloading:
>
>- if there is a request to reload a macro, which is not the last one
> in stack, *all* the macros starting from the requested one and up
> to the last one in stack have to be reloaded in order they have been
> put in stack.
>
>Masa, would this procedure work from your point of view?
>
> -pasha
Above statement is correct.
First, I explain what is already implemented in CINT. If you try to reload
a file which is not the last one in stack, CINT automatically unloads all
the macros starting from the requested one, then reloads only the requested
macro. For example,
.L file2.C
file1.C file1.C file1.C
file2.C -------------> ---> file2.C
file3.C
file4.C
Now, if I am requested to add a feature to do reloading for file3.C and
file4.C, it is not difficult.
.R file2.C <<< New Reload command
file1.C file1.C file1.C
file2.C -------------> ---> file2.C
file3.C file3.C
file4.C file4.C
If this feature had been requested, I simply misunderstood it. I can do it.
Please let me know if this is needed.
Masaharu Goto
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:43:31 MET