> The encoding simply
> takes characters that are special to JMeter and
> escapes them (${}(),\) making it easy to write an
> encoded function by hand.
>
> For instance, if a regex function referenced a
> variable it would now look something like:
> ${__regexFunction(\$\{pattern\},\$1\$,1,,,)}. The
> Function Helper Dialog has been updated as well as all
> of the standard functions.
This seems backwards from what we discussed. Shouldn't the characters only
need escaping if the user is trying to use them as literals in a string (as a
parameter value, for instance)?
So:
${__regexFunction(${pattern},$1$,1,,,)}
means that the regex function will use as it's pattern, whatever the value of
the ${pattern} variable is.
${__regexFunction(\$\{pattern\},$1$,1,,,)}
means that the regex function will use "${pattern}" as it's regular
expression.
This would be far preferable, in my view, because then characters are only getting
escaped in unusual situations. Make sense?
-Mike
>
> I'll try to get this in the docs this week.
>
> Any questions?
>
> Thad
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, more
> http://taxes.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Michael Stover
[EMAIL PROTECTED]
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
