Hi,
Currently we use a patches version of the parser (1.6R7) that does things
like this:
functionSourceEnd =
decompiler.markFunctionEnd(functionSourceStart);
functionSourceEnd = ts.getCursor(); <<<<< added this line to
override the decompiler source end.
because we dont need the encoded source starts ending but we need the real
source start and endings.
We == DLTK which is a plugin for dynamic languages support in eclipse
Beause we parse the js files and then use the beginning and ending to map
everything to the right areas (like the outline view)
Now my question is what is that encoded source beginnings and endings who is
using that for what?
It seems to me that real source values are way more usefull.
But the question is does 1.7RX with the new AST now have the real source
start/ends? So that for tooling this is easier?
Would it be something that i patch the code and make besides these:
public final int getEncodedSourceStart() {
return encodedSourceStart;
}
public final int getEncodedSourceEnd() {
return encodedSourceEnd;
}
also
public final int getSourceStart() {
return sourceStart;
}
public final int getSourceEnd() {
return sourceEnd;
}
But this patch would be for now 1.6. But is there still something planned
for 1.6?
johan
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
