Re: no output files

On Wed, Nov 19, 2008 at 7:18 AM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>> The fact that in this case a file (empty) is still created
>> seems like a bug.
>
> It is actually a deliberate design choice, after a reasoned debate.
>

Yes, I understand that reasoning.

So, "output" and "output file" are two different things.


-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play


> Given that an XSLT stylesheet can be used to create an external general
> parsed entity, and that an external general parsed entity can legitimately
> be "empty", we felt that
>
> <xsl:param name="n" as="xs:integer"/>
> <xsl:template match="/">
>  <xsl:for-each select="1 to $n">
>    <xsl:text>baa</xsl:text>
>  </xsl:for-each>
> </xsl:template>
>
> should produce an EGPE whose value contains $n repetitions of the string
> 'baa', in all cases including when $n=0.
>
> It's also relevant for example if the output of the stylesheet is a list of
> data errors found in the source document. If there are no such data errors,
> the next stage in the processing pipeline should expect to see an empty
> list. It's quite possible in this case that the result will be passed to the
> next stage as an XDM tree, without being serialized.
>
> Michael Kay
> http://www.saxonica.com/