Hi all,

I noticed in the call graph I generated from running csound4, if using
ccsound.c and csound.c, reset() gets called twice in a run, once at the
end of musmon(), and again when calling csoundCleanup().  

Looking at csound5 cvs, musmon2 calls reset as well, and maybe there's a
potential for calling reset() twice here as well if csoundCleanup() is
called.

I think this would happen only if using the csound host API to run, but
not if using jpff_glue.c.  Don't know if it's a problem to run cleanup()
twice in a run, but seemed strange so I thought I'd mention it.

Thanks,
steven

I suspect you are stuck with them for now. Both CsoundReset and 
CsoundCleanup need to be rendered redundant, by returning their 
functionality to a restructured internal architecture of Csound, which 
needs to be able to clean up after itself! The RESET and GLOBALS issues 
are deeply intertwined, needless to say. Eliminating the latter will 
eliminate most, if not all, of RESET too.

My main hope is that, at least, those calls do not proliferate any 
further than they already have.

Richard Dobson

stevenyi wrote:
> Hi all,
> 
> I noticed in the call graph I generated from running csound4, if using
> ccsound.c and csound.c, reset() gets called twice in a run, once at the
> end of musmon(), and again when calling csoundCleanup().  
> 
> Looking at csound5 cvs, musmon2 calls reset as well, and maybe there's a
> potential for calling reset() twice here as well if csoundCleanup() is
> called.
> 
> I think this would happen only if using the csound host API to run, but
> not if using jpff_glue.c.  Don't know if it's a problem to run cleanup()
> twice in a run, but seemed strange so I thought I'd mention it.
> 
> Thanks,
> steven
> 
> 
> 

there at least used to be an if (runningincomponents) around the
cleanup() call in musmon.  at least with csound4 perhaps
runningincomponents should be renamed to usingAPI
or something and it also needs to be moved into GLOBALS - maybe something
already has been done with that in cs5, i will finally
hook into cvs next week and check it out -- sorry if im out of touch
with current developments

-m





On Sat, 22 Nov 2003, stevenyi wrote:

> Hi all,
>
> I noticed in the call graph I generated from running csound4, if using
> ccsound.c and csound.c, reset() gets called twice in a run, once at the
> end of musmon(), and again when calling csoundCleanup().
>
> Looking at csound5 cvs, musmon2 calls reset as well, and maybe there's a
> potential for calling reset() twice here as well if csoundCleanup() is
> called.
>
> I think this would happen only if using the csound host API to run, but
> not if using jpff_glue.c.  Don't know if it's a problem to run cleanup()
> twice in a run, but seemed strange so I thought I'd mention it.
>
> Thanks,
> steven
>
>
>