I do not think there is a convenient way to do this. I imagine one
could the compile step, then take the CSOUND* and walk every data
object and write it out to disk or copy to memory (depending on if you
are trying to restart from disk or in memory).  I do not know if there
is any technique like this in C to do a deep copy of a struct like
there is in Java or other languages; if so, then one could do that
with the CSOUND* and then just start processing with the reserialized
copy or in-memory copy.

On Mon, Jan 19, 2009 at 5:53 AM, Pinball <ads_box@hotmail.com> wrote:
>
> Is it possible, after compiling a csd or orc/sco file,
> to store the compilation results? Let's call them... CODE.
>
> Is it possible/safe to skip the csoundCompile call by
> importing the previously compiled CODE?
>
> If the answer is yes, which are the variables
> affected by the compilation?
>
> Thanks
>
> --
> View this message in context: http://www.nabble.com/Skipping-CSound-Compilation-tp21540668p21540668.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net