For review: forward_move always moves

[Erwan Jahier]

Fergus Henderson wrote:
> When you've tested this change, please post a revised diff with a revised
> log message.
> 
> Thanks,
>         Fergus.
> 


runtime/mercury_trace_external.c:
	Start to find a forward matching event from the next event rather
	from the current event (according to Opium specification,
	forward_move(nop, nop, ..., nop) should move one event forward).
        


Index: mercury_trace_external.c
===================================================================
RCS file:
/home/mercury1/repository/mercury/runtime/mercury_trace_external.c,v
retrieving revision 1.3
diff -u -r1.3 mercury_trace_external.c
--- mercury_trace_external.c	1998/07/13 22:44:12	1.3
+++ mercury_trace_external.c	1998/07/23 14:04:49
@@ -312,7 +317,6 @@
 	Integer debugger_request_type;
 	Word var_list;
 
-do_search:
 	if (searching) {
 		/* XXX should also pass registers here,
 		   since they're needed for checking for matches with the
@@ -343,20 +347,20 @@
 				}
 				search_data = debugger_request;
 			        searching = TRUE;
-				goto do_search;
+				return;
 			       			      		
 			case MR_REQUEST_CURRENT:
 				if (MR_debug_socket) {

-- 
R1.