[m-dev.] trivial diff: update some comments
Mark Anthony BROWN
dougl at cs.mu.OZ.AU
Sat Feb 19 03:09:42 AEDT 2000
Estimated hours taken: 0.1
trace/mercury_trace_vars.h:
Fix/improve some comments.
Index: mercury_trace_vars.h
===================================================================
RCS file: /home/mercury1/repository/mercury/trace/mercury_trace_vars.h,v
retrieving revision 1.4
diff -u -r1.4 mercury_trace_vars.h
--- mercury_trace_vars.h 1999/12/10 04:24:09 1.4
+++ mercury_trace_vars.h 2000/02/18 16:04:34
@@ -7,7 +7,7 @@
** that are live at a given program point.
**
** When execution arrives at an event, the debugger should call the function
-** MR_trace_point_init_vars to initialize this module's data structures
+** MR_trace_init_point_vars to initialize this module's data structures
** to reflect the variables that are live at that event. During the processing
** of the various debugger commands while at that event, the debugger may
** call MR_trace_set_level zero or more times to change this module's notion
@@ -78,7 +78,8 @@
/*
** Return the name, type and value of the specified variable in the specified
-** locations, except those which are NULL.
+** locations, except those which are NULL. Variable number n must be
+** in the range 1..MR_trace_var_count().
*/
extern const char *MR_trace_return_var_info(int n, const char **name_ptr,
--
Mark Brown, PhD student )O+ | "Another of Fortran's breakthroughs
(m.brown at cs.mu.oz.au) | was the GOTO statement, which was...
Dept. of Computer Science and Software | uniquely simple and understandable"
Engineering, University of Melbourne | -- IEEE, 1994
--------------------------------------------------------------------------
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