FileState.getAnalyzedAst() does a reanalyze
This behavior is somewhat unexpected, because
FileState.getCurrentAst()
also doesn’t do a reparse.If nobody minds, I would like to change the code to:
public IStrategoTerm getAnalyzedAst() throws BadDescriptorException { StrategoObserver observer = getDescriptor().createService(StrategoObserver.class, getParseController()); return observer.getResultingAst(getResource()); }
Otherwise, I think we need a
Submitted by Oskar van Rest on 6 June 2013 at 19:04getCurrentAnalyzedAST()
Issue Log
On 7 June 2013 at 11:56 Lennart Kats commented:
Since analysis is always scheduled with a considerable delay, I think adding a
getCurrentAnalyzedAst()
may be better.
On 8 June 2013 at 06:49 Oskar van Rest commented:
ok, fixed
On 8 June 2013 at 06:49 Oskar van Rest closed this issue.
Log in to post comments