[m-rev.] for review: add `info' declarative debugger response

Ian MacLarty maclarty at cs.mu.OZ.AU
Wed Mar 2 11:19:22 AEDT 2005


On Sat, Feb 26, 2005 at 11:32:34PM +1100, Julien Fischer wrote:
> 
> You need to add the info response to the user guide as well.
> 

Done.  I also slipped in some extra comments about the new --resume option.

Index: doc/user_guide.texi
===================================================================
RCS file: /home/mercury1/repository/mercury/doc/user_guide.texi,v
retrieving revision 1.421
diff -u -r1.421 user_guide.texi
--- doc/user_guide.texi	18 Feb 2005 04:05:33 -0000	1.421
+++ doc/user_guide.texi	2 Mar 2005 00:12:30 -0000
@@ -4088,9 +4088,18 @@
 Commence procedural debugging from the current point.
 This command is notionally the inverse of the @samp{dd} command
 in the procedural debugger.
+The session can be resumed with a @samp{dd --resume} command.
 @item abort
 End the declarative debugging session and return to
-the event at which the @samp{dd} command was given.
+the event at which the @samp{dd} command was given.  
+The session can be resume with a @samp{dd --resume} command.
+ at sp 1
+ at item info
+List the filename and line number of the predicate the current question
+relates to as well as the filename and line number where the predicate 
+was called (if this information is available).  Also print some information
+about the state of the bug search, such as the current search mode and
+how many events are yet to be eliminated.
 @sp 1
 @item help
 Summarize the list of available commands.

I also changed the CVS log:

doc/user_guide.texi
	Document the info command.  
	
	Say that the --resume option can be used to resume an aborted or pd'd
	session.

> > +	io.nl(OutStream, !IO),
> > +	io.write_string(OutStream, InfoMessage, !IO),
> > +	io.nl(OutStream, !IO),
> > +	io.nl(OutStream, !IO),
> 
> That would be more concise as:
> 
> 	io.format(OutStream, "\n%s\n\n", [s(InfoMessage)], !IO)
> 

Changed, thanks.

> > +	Node = get_edt_node(SearchSpace, LastQuestionId),
> > +	edt_question(Analyser ^ io_action_map, Store, Node,
> > +		OracleQuestion),
> > +	Response = oracle_question(OracleQuestion).
> 
> How large are the FieldNames and Data lists likely to get?  It may be
> worth constructing them in reverse and then reversing them before you
> need them rather than always appending to the end of a list.
> 

They are max 4 elements at the moment, so I don't think it'd be worth 
doing that.

Cheers,

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



More information about the reviews mailing list