I mean all the things that are in runsequence, weave and compile methods
like (bold is functional code, green is what I added to support eclipse,
black is original ABC code)
// phase check exceptions
if (!abc.main.Debug.v().dontCheckExceptions) {
monitor.isCanceled();
monitor.setPhase("Exceptions check");
*checkExceptions();*
AbcTimer.mark("Exceptions check");
Debug.phaseDebug("Exceptions check");
monitor.setProgress(61);
}
// phase inline advice
{
monitor.isCanceled();
monitor.setPhase("Inline Advice");
*inlineAdvice();*
monitor.setProgress(62);
}
Wouter
On Tue, Aug 12, 2008 at 5:02 PM, Eric Bodden <eric.bodden_at_mail.mcgill.ca>wrote:
> Hi Wouter.
>
> Which passes are you referring to? The polyglot passes that
> analyze/rewrite the AST? If so please note that any new extensions to
> abc will be based on JastAdd (see packages abc.ja.*) and that those
> extensions don't really have the notion of passes any more. (There are
> still some coarse passes like jimplification etc. but not very many.)
>
> In general I don't think that there was much of a plan for
> formalization, exactly for the reason that we switched to JastAdd.
>
> Hope that helps.
>
> Eric
>
> 2008/8/12 Wouter De Borger <w.deborger_at_gmail.com>:
> > Hi,
> >
> > Is there a plan to formalize the pass/stage scheduling in the ABC?
> > (if so, I'd love to help)
> >
> > Each pass/stage begins with a call to abortIfErrors() and ends with a
> call
> > to both the timer and debug-logger.
> >
> > I'm now adding a progress monitor and cancellation support, (for eclipse)
> > which adds a call before and after each stage,....
> > This requires a lot of scattered code and it doesn't exactly make the
> code
> > more readable,....
> >
> >
> > Wouter
> >
>
>
>
> --
> Eric Bodden
> Sable Research Group
> McGill University, Montréal, Canada
>
>
Received on Tue Aug 12 2008 - 16:14:54 BST
This archive was generated by hypermail 2.2.0 : Tue Aug 12 2008 - 17:00:11 BST