On Wed, Aug 28, 2013 at 8:36 PM, HaveF <[email protected]> wrote:
https://gist.github.com/HaveF/6373152
>
Thanks for this. The erroneous message about inserting an @ignore
directive was easy to fix.
The real bug is that code such as::
app.listen(port, function() {
console.log("Listening on " + port);
});
will generate a complaint about function "function" not ending in a newline.
Indeed, the '}' on the last line is followed by a ')', because the
definition of function is embedded in the call to app.listen(!)
It's not at all clear what to do about this and related cases. Indeed,
it's hard to know whether we would actually want to put such a lightweight
definition in a node of its own. Otoh, such embedded functions are common,
and we often *would* rather put them in separate nodes.
At present, the javascript import code is very simple: it just sets some
switches in the base scanner class and overrides the base class's notion of
what a string is. Clearly, at least some special-purpose hacking will be
required. My first thought is just to suppress the warning. This *might*
work, provided that the scanning can resume properly at the ')' and ';'
that follows the '}'. We shall see.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
