| Hi Denis,
Thanks for your feedback.
VJET has a special js comment parser which inspects for type hints. These hints we call vjetdoc.
The comment you have
// > // Tag description.
// > method(window).hashchange( function(e) {
// > var hash = location.hash;
// > ...
// > });
collides with vjet doc comments... just change //> to // ! > or remove the greater than sign.
Such as:
// // Tag description.
// method(window).hashchange( function(e) {
// var hash = location.hash;
// ...
// });
Thanks,
Justin
Justin,
I created VJetProject, added test.js file that contains snipped
below and got 5 errors for this snippet. Meantime I can run it
without any problems as Vjet Web project on FireFox and it works
as expected without any errors, JSDT works correct in this case.
test.js content
// > // Tag description.
// > method(window).hashchange( function(e) {
// > var hash = location.hash;
// > ...
// > });
window.alert("test");
Description Resource Path Location Type
VJET comment error: Lexical error at line 1, column 3.
Encountered: "/" (47), after : "" For comment :// > // Tag
description. test.js /js-vjet/src line 3 VJET Problem
VJET comment error: Lexical error at line 1, column 18.
Encountered: "h" (104), after : "." For comment :// >
method(window).hashchange( function(e) { test.js
/js-vjet/src line 4 VJET Problem
VJET comment error: Lexical error at line 1, column 14.
Encountered: "=" (61), after : "" For comment :// > var hash
= location.hash; test.js /js-vjet/src line 5 VJET
Problem
VJET comment error: Syntax error at ... delete this token For
comment :// > ... test.js /js-vjet/src line 6
VJET Problem
VJET comment error: Syntax error at } delete this token For
comment :// > }); test.js /js-vjet/src line 7 VJET
Problem
Denis
On 01/29/2013 10:29 AM, Justin Early wrote:
Hi John,
Thanks for the feedback.
someVar = 1 + 2
++someVar
Yes I see the syntax error in VJET too... created bug for
this.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=399417
Thanks for the info didn't see this case in our test suite.
For this
For our variant of JSDT [1] we disabled
JSDT's problem checking and
instead plan to use an optimized version of JSHint-eclipse
[2].
Do you see any issues with performance? JSDT has to parse the
js file for search and code assist, then jshint has to parse and
report issues.
Justin
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
|
