I would like it if you would add something like
(i really like it when modules are examples of how to use themselves):
package main;
unless(caller) {
$\ = "\n\n#######\n\n";
my $js_parser = Parse::JavaScript->new();
print $js_parser->parse(<<'_EOJS_');
function foo(bar){ // JS Comment
window.location = "http://www." + bar + '.com'
}
var quux = 68;
var baz = quux++;
_EOJS_
print $js_parser->parse(q[
while(1) {
document.write(" die ");
}
]);
print $js_parser->parse(q[
do {
document.write(" die ");
} while (1);
]);
print $js_parser->parse(q[
for(;;) {
document.write(" die ");
}
]);
print $js_parser->parse(q[
document.write( /(\w+)/g.exec("foo bar") );
]);
print $js_parser->parse('
document.write( /[^\]\[](\w+)/g.exec("foo bar") );
');
print $js_parser->parse(q{
/* HERE GOES AN ERROR (good job)
});
}
Good job (++).
Do you know of any valid javascript which might cause an error ?
( the examples above are all valid, and all validate until /* HERE GOES AN ERROR (good job))
____________________________________________________ ** The Third rule of perl club is a statement of fact: pod is sexy.
-
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.
|