[m-rev.] for review: Allow --xml browse option from within declarative debugger

[Julien Fischer]

On Sat, 19 Feb 2005, Ian MacLarty wrote:

> > > 	declarative debugger.
> > >
> > > 	Export the browser_persistent_state type so the field access functions
> > > 	can be used from browse.m.
> > >
> > Is that necessary?  Why don't you just export the access functions for
> > the relevant fields?
> >
>
> I didn't know that was possible.  How do I do that?
>
See section 3.4.3 of the reference manual.

> > > @@ -145,11 +147,24 @@
> > >
> > >  %---------------------------------------------------------------------------%
> > >
> > > -	% An abstract data type that holds persistent browser settings.
> > > +	% An data type that holds persistent browser settings.
> > >  	% This state must be saved by the caller of the browse module
> > >  	% between calls.
> > >  	%
> >
> > If only a few of these fields need to be exported, then exporting
> > the field acces functions may be a better choice than making the
> > type non-abstract.
> >
>
> Is it just a case of putting:
>
> :- func xml_browser_cmd(browser_persistent_state) = maybe(string).
>
> in the interface?  What about the field update function?
>
Putting the following in the module interface should suffice:

:- func browser_persistent_state ^ xml_browser_cmd = maybe(string).
:- func browser_persistent_state ^ xml_browser_cmd := maybe(string) =
	browser_persistent_state.

Julien.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------