Hi, I think this is caused by the function representation in the docs. 'string xml' does not imply the default is a filename and the time that users use a scrollbar seems to have passed.
I've seen this several times at the Sablotron list as well. Below is an attempt to make people aware of it: Index: xslt-process.xml =================================================================== RCS file: /repository/phpdoc/en/reference/xslt/functions/xslt-process.xml,v retrieving revision 1.3 diff -u -r1.3 xslt-process.xml --- xslt-process.xml 22 May 2002 08:58:31 -0000 1.3 +++ xslt-process.xml 29 Aug 2002 10:47:27 -0000 @@ -11,18 +11,36 @@ <methodsynopsis> <type>mixed</type><methodname>xslt_process</methodname> <methodparam><type>resource</type><parameter>xh</parameter></methodparam> - <methodparam><type>string</type><parameter>xml</parameter></methodparam> - <methodparam><type>string</type><parameter>xsl</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>result</parameter></methodparam> + <methodparam><type>string</type><parameter>xmlcontainer</parameter></methodparam> + <methodparam><type>string</type><parameter>xslcontainer</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>resultcontainer</parameter></methodparam> <methodparam choice="opt"><type>array</type><parameter>arguments</parameter></methodparam> <methodparam choice="opt"><type>array</type><parameter>parameters</parameter></methodparam> </methodsynopsis> <para> The <function>xslt_process</function> function is the crux of the new XSLT extension. It allows you to perform an XSLT transformation using - almost any type of input source. This is accomplished through the use of - argument buffers -- a concept taken from the Sablotron XSLT processor - (currently the only XSLT processor this extension supports). + almost any type of input source - the containers. This is accomplished + through the use of argument buffers -- a concept taken from the Sablotron + XSLT processor (currently the only XSLT processor this extension supports). + The input containers default to a filename 'containing' the document to be + processed. The result container defaults to a filename for the transformed + document. If the result container is not specified - i.e. + <parameter>NULL</parameter> - than the result is returned. + </para> + <para> + <warning> + <simpara> + This function has changed it's arguments, sinceversion 4.0.6. Do NOT + provide the actual xml or xsl content as 2nd and 3rd argument, as this + will create a segmentation fault, in Sablotron versions up to and + including 0.95. + </simpara> + </warning> + </para> + <para> + Containers can also be set via the <parameter>$arguments</parameter> + array (see below). </para> <para> The simplest type of transformation with the @@ -151,9 +169,13 @@ </example> </para> <para> - Finally, the last argument to the <function>xslt_process</function> function is any parameters - that you want to pass to the XSLT document. These parameters can then be accessed within - your XSL files using the <xsl:param name="parameter_name"> instruction. + Finally, the last argument to the <function>xslt_process</function> + function represents an array for any top-level parameters that you want to + pass to the XSLT document. These parameters can then be accessed within + your XSL files using the <xsl:param name="parameter_name"> + instruction. The parameters must be UTF-8 encoded and their values will be + interpreted as strings by the Sablotron processor. In other words - you + cannot pass node-sets as parameters to the XSLT document. </para> </refsect1> </refentry> At 09:29 8/29/2002 +0000, [EMAIL PROTECTED] wrote: > ID: 19170 > Updated by: [EMAIL PROTECTED] > Reported By: [EMAIL PROTECTED] >-Status: Open >+Status: Bogus > Bug Type: XSLT related > Operating System: windows 2000/sp3 > PHP Version: 4CVS-2002-08-29 > New Comment: > >Not enough information was provided for us to be able >to handle this bug. Please re-read the instructions at >http://bugs.php.net/how-to-report.php > >If you can provide more information, feel free to add it >to this bug and change the status back to "Open". > >Thank you for your interest in PHP. > > > >Previous Comments: >------------------------------------------------------------------------ > >[2002-08-29 05:21:51] [EMAIL PROTECTED] > >Hello! > >I wrote about bug more than one week ago. >Now I install apache2.0.40, install lastest PHP version from CVS and >got some bug. >apache was crashed when I call function xslt_process(); >I provide arguments for xslt_process via array. >Apache generate next error: >"Unhandled exception in Apache.exe (MSVCRT.DLL) 0xC0000005: Access >Violation > >Stack overview: >MSVCRT! 78005034() >MSVCRT! 78004f32() >MSVCRT! 780253cb() >MSVCRT! 780252f3() >PHP4TS! 00dbf870() > >my project was stopped for two weeks... >Please help me. > > >------------------------------------------------------------------------ > > >-- >Edit this bug report at http://bugs.php.net/?id=19170&edit=1 Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua <@Logan> I spent a minute looking at my own code by accident. <@Logan> I was thinking "What the hell is this guy doing?"
Index: xslt-process.xml =================================================================== RCS file: /repository/phpdoc/en/reference/xslt/functions/xslt-process.xml,v retrieving revision 1.3 diff -u -r1.3 xslt-process.xml --- xslt-process.xml 22 May 2002 08:58:31 -0000 1.3 +++ xslt-process.xml 29 Aug 2002 10:47:27 -0000 @@ -11,18 +11,36 @@ <methodsynopsis> <type>mixed</type><methodname>xslt_process</methodname> <methodparam><type>resource</type><parameter>xh</parameter></methodparam> - <methodparam><type>string</type><parameter>xml</parameter></methodparam> - <methodparam><type>string</type><parameter>xsl</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>result</parameter></methodparam> + +<methodparam><type>string</type><parameter>xmlcontainer</parameter></methodparam> + +<methodparam><type>string</type><parameter>xslcontainer</parameter></methodparam> + <methodparam +choice="opt"><type>string</type><parameter>resultcontainer</parameter></methodparam> <methodparam choice="opt"><type>array</type><parameter>arguments</parameter></methodparam> <methodparam choice="opt"><type>array</type><parameter>parameters</parameter></methodparam> </methodsynopsis> <para> The <function>xslt_process</function> function is the crux of the new XSLT extension. It allows you to perform an XSLT transformation using - almost any type of input source. This is accomplished through the use of - argument buffers -- a concept taken from the Sablotron XSLT processor - (currently the only XSLT processor this extension supports). + almost any type of input source - the containers. This is accomplished + through the use of argument buffers -- a concept taken from the Sablotron + XSLT processor (currently the only XSLT processor this extension supports). + The input containers default to a filename 'containing' the document to be + processed. The result container defaults to a filename for the transformed + document. If the result container is not specified - i.e. + <parameter>NULL</parameter> - than the result is returned. + </para> + <para> + <warning> + <simpara> + This function has changed it's arguments, sinceversion 4.0.6. Do NOT + provide the actual xml or xsl content as 2nd and 3rd argument, as this + will create a segmentation fault, in Sablotron versions up to and + including 0.95. + </simpara> + </warning> + </para> + <para> + Containers can also be set via the <parameter>$arguments</parameter> + array (see below). </para> <para> The simplest type of transformation with the @@ -151,9 +169,13 @@ </example> </para> <para> - Finally, the last argument to the <function>xslt_process</function> function is any parameters - that you want to pass to the XSLT document. These parameters can then be accessed within - your XSL files using the <xsl:param name="parameter_name"> instruction. + Finally, the last argument to the <function>xslt_process</function> + function represents an array for any top-level parameters that you want to + pass to the XSLT document. These parameters can then be accessed within + your XSL files using the <xsl:param name="parameter_name"> + instruction. The parameters must be UTF-8 encoded and their values will be + interpreted as strings by the Sablotron processor. In other words - you + cannot pass node-sets as parameters to the XSLT document. </para> </refsect1> </refentry>
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php