RE: EmbPerl 1.20 hash/href problem?
>
> The following testcast fails under 1.20. Basically, if there is a hash
> deref inside an HREF tag, without quotes, you get the following error:
>
> [27723]ERR: 13: Line 4: Missing right +]
>
> If you quote the HREF or create a temporary variable to hold the
> hash deref
> everything works fine.
>
>[..]
>
>
> {TOPICID} +]>Link
I know this problem. As you write above, writing
Link
will solve the problem. Because parser tries to find the end of the HREF arg
and if not quoted the end is after the first space or when he finds a >.
Because the quoting doesn't hurt (as far as I see) I haven't changed this
until now, to make the parser not to compilcated and therfor not to slow.
Gerald
-
Gerald Richterecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925151
WWW:http://www.ecos.de Fax: +49 6133 925152
-
Re: EmbPerl 1.20 hash/href problem?
> I know this problem. As you write above, writing > > Link > > will solve the problem. Because parser tries to find the end of the HREF arg > and if not quoted the end is after the first space or when he finds a >. > Because the quoting doesn't hurt (as far as I see) I haven't changed this > until now, to make the parser not to compilcated and therfor not to slow. > > Gerald Is this, or will this be, documented somewhere? Seeing as it is a kludge, even if it does help performance somewhat, is this going to be fixed in the future or is this Working As Designed? Any chance of having the "end of tag" logic changed to ignore characters inside the EmbPerl braces ( [+ ... +] ) since this is the most likely place to cause problems? Thanks. -- James Sheridan-Peters Sr. Application Developer Community of Science (410) 563-2378 x297 [EMAIL PROTECTED]
RE: EmbPerl 1.20 hash/href problem?
> > Is this, or will this be, documented somewhere? I don't think so :-( > Seeing as it is a kludge, > even if it does help performance somewhat, is this going to be > fixed in the > future or is this Working As Designed? Any chance of having the "end of > tag" logic changed to ignore characters inside the EmbPerl braces ( [+ ... > +] ) since this is the most likely place to cause problems? > I put it on the TODO list, to rework that part of the parser. Maybe I find a way to do it without wasting too much performance. Gerald - Gerald Richterecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice:+49 6133 925151 WWW:http://www.ecos.de Fax: +49 6133 925152 -
