[m-dev.] for review: redo events in shallow traced procedures
Zoltan Somogyi
zs at cs.mu.OZ.AU
Tue Aug 24 15:31:29 AEST 1999
> > + % trace__reserved_slots.
> > + require(unify(Lval, framevar(5)),
> > + "from-full flag not stored in expected slot"),
> > Code = node([
> > mkframe(temp_frame(nondet_stack_proc),
> > - do_trace_redo_fail)
> > + do_trace_redo_fail_shallow)
> > + - "set up shallow redo event"
> > + ])
> > + ;
> > + TraceType = deep_trace,
> > + Code = node([
> > + mkframe(temp_frame(nondet_stack_proc),
> > + do_trace_redo_fail_deep)
> > - "set up deep redo event"
> > ])
> > + )
> > ;
> > Code = empty
> > ).
>
> Is this indented correctly? It looks like the last four unchanged lines
> need to be indented one level further.
Yes it is. With diff -b, if you introduce white space on a line but otherwise
keep it the same (which is what I did there), that line will look misaligned
on the diff wrt new lines, even if they are aligned in the new source code.
Zoltan.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions: mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------
More information about the developers
mailing list