At 3:02 PM +0000 3/25/02, Chris Allen wrote:
>Our main ISP just upgraded their Embperl to 2.0b4 without telling
>us - :-( Unfortunately, nearly all our code is in the form:
>
>[+ some_statememt(); +]
>
>so it breaks because of the semicolon. We have thousands of lines of web site
>code that don't work now!
That's a bizarre upgrade decision. Not only has it been made clear
that Embperl 2.0 isn't production ready, but that's 3 revs out of
date. If they'd made the move at b7 it would be okay, because they
could run both (in theory).
Gerald's on vacation for two weeks, but I'm not aware of any
workaround other than taking out the semi-colons (which will work in
both versions) or going back to Embperl. There is one global change
you could make, but it's kind of ugly:
[+ do {some-statement(); } +]
will work regardless of how many statements there are, and whether or
not they have semi-colons. That also works in the old version.
But the restriction now is that the code inside [++] must be a
single complete (up to but not including the semi-colon) statement.
Something to do with out the new parser is written.
I'd highly recommend that the ISP go back to HTML::Embperl 1.x and if
they are going to move to 2.0, do it with Embperl 2.0b7.
--
Kee Hinckley - Somewhere.Com, LLC
http://consulting.somewhere.com/
[EMAIL PROTECTED]
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
