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

[Anya Helene Bagge <anya@xxxxxxxxx>]

On 02/12/2011 11:41 PM, Jurgen Vinju wrote:
> No quick answer here. The psrser must run synchronously with the ui
> thread i think. Does that help? Otherwise please ask this pn imp-dev!

We are on imp-dev... ;)

Parser runs asynchronously (as a Job) after the first initial parse.

-anya

> Sent from my iPhone
>
> On 12 feb. 2011, at 22:43, Anya Helene Bagge<anya@xxxxxxxxx>  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
> >
> >
> > _______________________________________________
> > imp-dev mailing list
> > imp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/imp-dev
> _______________________________________________
> imp-dev mailing list
> imp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/imp-dev