[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Seeking Examples of XSLT Memory Stress

• To: "'Bob Foster'" <bob@o...>
• Subject: RE: Seeking Examples of XSLT Memory Stress
• From: "Michael Kay" <mike@s...>
• Date: Thu, 18 Aug 2005 00:06:37 +0100
• Cc: <xml-dev@l...>
• In-reply-to: <4303C0BF.7010706@o...>
• Thread-index: AcWjfvpFAb4g3isLSlu3rw326VfxpgAAN10w

> 
> But then the semantics of unload are that those two 
> guarantees no longer 
> apply. Is that too hard to specify?
> 

Yes, it really messes up the formal semantics if calling the same function
twice with the same arguments can produce different results.

Implementations can muddle through with this kind of thing, by adding the
odd conditional to the optimizer, but it's very hard to express the
consequences formally.

Michael Kay
http://www.saxonica.com/ 

• References:
  • Re: Seeking Examples of XSLT Memory Stress
    • From: Bob Foster <bob@o...>

• Prev by Date: Re: Seeking Examples of XSLT Memory Stress
• Next by Date: Re: License Feedback -- health and safety issues
• Previous by thread: Re: Seeking Examples of XSLT Memory Stress
• Next by thread: Re: License Feedback -- health and safety issues
• Index(es):
  • Date
  • Thread