Actually - it doesn't work for me also, except for some strange exceptions,
I haven't been
able to put a finger on.
What does work (and also the reason why I think eval() SHOULD work), is
writing the
output to a file and then including that file.
You then are creating a strange paradox, and the whole thing becomes quite
unstable:
1) PHP 4 checks a file and it's includes for parser errors.
2) It then pre-compiles the page
3) It executes the page:
--> You create and write a file
--> You include the file, which didn't exist in fase 1.
So - I since then have left the whole issue alone and try to work around
it. In case where
I can't I use a crontab to write the includes every now and then.
At 12:10 19-7-2001 -0700, you wrote:
>Well, none of this works for me... Even after a lot of testing.
>
>Did compile with a strange option or soemthing?
>
>
>-----Original Message-----
>From: Melvyn Sopacua [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, July 18, 2001 2:19 PM
>To: Sablotron Mailing List
>Subject: RE: [Sab] including php in xsl
>
>
>
>I got sick of the eval() errors, but if your eval works well,
>try:
>
><xsl:processing-instruction name="php">echo
>$var</xsl:processing-instruction>
