Re: Serialized continuation size

On Mon, Apr 24, 2006 at 08:22:13AM -0700, Dan wrote:
> Hi Scott,
> 
> I'm not subscribed to sisc-users, and don't know how
> to create a proper reply within the existing
> "Serialized continuation size" thread.

SISC users is an open list, so you should be able to reply to 
[email protected] in the future.

> 
> A few points:
> 
> * it would be nice to have something like Chicken
> Scheme's chicken-dump (which displays the structure of
> a serialization file)

Raise a feature request for it on SourceForge.  It would be an 
interesting tool.

> 
> * you said
> 
> > Other, user defined procedures may be
> > serialized however.
> 
> For example, the definition (body) of a
> globally-defined procedure might be serialized? How
> about a procedure defined within a module?

Actually, checking now, if a procedure is defined in a named symbolic 
environment, a reference to that procedure is serialized instead.  So 
toplevel references, including toplevel defined module exports, won't be 
serialized in there entirety.

> How about the code making up the continuation (i.e.
> the remaining statements to be executed)?

Active microexpressions are serialized, so yes, some of the compiled 
portions of any procedure can be there.

> 
> As a SISCweb user/customizer, I certainly don't want
> any code fragments to be ever serialized -- only
> perhaps references to code fragments. How do I ensure
> this? Do I need to create new heap files?

What are you concerned about exactly?  

  Scott


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642