comment on

document.write('"hello Fred\'s world"');
[download]

works fine as does the excessively complex '"hello \"Fred\'s world\" "'

This means that you can safely do a s(["'])/\$1/g server side thingy and all is OK. You can also do most perl regexen in javascript. However there is a bug in IE that means that string.split(/(?:a|b)/) causes the JS engine to stop - although string.split(/(a|b)/) does work ok. On the other hand in Mozilla string.split(/(a|b)/) crashes the browser - this is a known bug and may be fixed in 1.2 - which makes cross-browser support somewhat problematical! However the example below works fine

ss = ", (?:\S+\. )*";
sre = (document.all)?/, (\S+\. )*/:new RegExp(", (?:\\S+\\. )*");
// later on
a = data.split(sre );
[download]

update The mozilla bug is 163323

Dingus

Enter any 47-digit prime number to continue.

In reply to Re: Template-output quoting (Warning: Contains JavaScript) by dingus
in thread Template-output quoting (Warning: Contains JavaScript) by perlcgi

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks