Re: [imp-dev] first parse -- why run() and not schedule()?

["Robert M. Fuhrer" <rfuhrer@xxxxxxxxxxxxxx>]

Hi Anya,

Actually, that's a good point -- I don't see any reason why the first parse needs to happen synchronously.

I'll make the change to trunk and post here when it's committed...

On Feb 12, 2011, at 4:43 PM, Anya Helene Bagge wrote:

Hi,

I have a quick question: The first parse of a program when a new editor is opened seems to be done synchronously, which hangs Eclipse if the parse takes a long time, e.g. because the parse table is generated on demand (hello, Rascal!). Is there any particular reason why UniversalEditor.initiateServiceControllers() does

   fParserScheduler.run(new NullProgressMonitor());

instead of just

   fParserScheduler.schedule();

?

-anya

--
Cheers,
  -- Bob
--------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center

IMP Team Lead (http://www.eclipse.org/imp)
X10: Productivity for High-Performance Parallel Programming (http://x10-lang.org)