[m-rev.] for review: hidden events

[Mark Brown]

On 30-Aug-2002, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> For review by anyone.
> 
> The need for hidden events was documented by the recent discussion in
> mercury-developers.
> 
> Zoltan.
> 
> Estimated hours taken: 1
> 
> Implement a flag that can be used by the compiler to signal to the debugger
> that some events should be hidden from the user. The flag is not used yet.
> 
> compiler/continuation_info.m:
> compiler/layout.m:
> 	Make room for the flag in the data structures storing information about
> 	events.
> 
> compiler/layout_out.m:
> 	Output the flag in label layouts.
> 
> runtime/mercury_stack_layout.h:
> 	Define a field for the flag in label layouts.
> 
> compiler/trace.m:
> 	Specify "no" as the value of the hidden flag, for now. Later, when we
> 	add hidden events, we will specify "yes" for them.
> 
> compiler/code_info.m:
> compiler/stack_layout.m:
> 	Pass on the value of the hidden flag.
> 

This change seems okay, but I'm not entirely sure how it is intended
to be used.  Could you please elaborate on where the test for this flag
will be performed?

Cheers,
Mark.

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------