Hi Ken, Thanks for your response, I appreciate you thinking about the issue. I agree with your logic regarding the blocks...in theory the parser should be ignoring both of the blocks because neither should exist. The symptoms I'm seeing is that this is not the case.
Regarding having only one true block - yes, the problem occurs then as well, though it's a bit expected in that case because the table tags will be unbalanced. Thanks! Heath [EMAIL PROTECTED] On Sat, 11 Sep 2004 22:05:32 -0400 "[EMAIL PROTECTED] Systems" <[EMAIL PROTECTED]> wrote: > Heath, > > Have you tried setting only one of the conditions to '1' and leaving the > other at '0' (Both ways)? I am by no means even practiced in embperl, but I > would want to eliminate this combination as well. I'm thinking you will get > the same error whenever the two conditions do not match. I'm guessing the > 0-0 combination does not work because (again, I am guessing) the parser is > not finding the end tags because it does not consider the second block > because it is always "off" and so does not (or can not) know they exist. > > Also, try this stucture: > > [$ if (0) $] > > <table align='center' width='50%'> > <tr><td align='center' bgcolor='#66AA66'> > > Test! > > </td></tr> > </table> > > [$ else $] > > Test! > > [$ endif $] > > Or try this just to see if the error changes or does not appear: > > [$ if (0) $] > > <table align='center' width='50%'> > <tr><td align='center' bgcolor='#66AA66'> > > Test! > > [$ if (0) $] > </td></tr> > </table> > [$ endif $] > > [$ endif $] > > This way, if the first condition is false, the second condition block is > never evaluated and, according to what I see here, it shouldn't be, anyway. > > I'm probably wasting your time but I hope this helps, > > Ken > > -----Original Message----- > From: Heath Morrison [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 11, 2004 11:34 AM > To: [EMAIL PROTECTED] > Subject: Table Processing > > > Hello, > > First, let me say that I've been using Embperl 1.x since 1999 with > incredible success. I've used it in virtually all my web-based projects > since then. Thanks Gerald for something that truly is exactly what I've > needed for years and years. > > I've decided to make the push from 1.3 to 2.0. I'm having some trouble with > the table parsing (something that I've always felt was best left > disabled) in 2.0. Since I cannot disable it in 2.0 I've been working around > it, but I've hit a bit of a wall that I don't know how to get past. Please > advise why the following HTML fails to parse successfully, > > [$ if (0) $] > <table align='center' width='50%'> > <tr><td align='center' bgcolor='#66AA66'> > [$ endif $] > > Test! > > [$ if (0) $] > </td></tr> > </table> > [$ endif $] > > This generates the following crash message: > > Error (no description) Unstrutured forward jump > > ...notice that those 'if' blocks should not be entered. If I set those > conditions to '1' instead of '0' everything works as expected. If I remove > the if blocks (or comment them out with [# #]) everything works as expected. > > > My actual HTML is of course much more involved, but suffers from the same > problem outlined here. Please let me know if you guys have any suggestions. > In particular, if anybody can suggest a means of disabling table parsing > that would probably make me happiest :) > > Thanks again! > > Heath > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
