From 0a0177d3795ceb0eea9e0e803148df36038776a4 Mon Sep 17 00:00:00 2001 From: Brian Norris Date: Fri, 15 Feb 2013 18:08:09 -0800 Subject: [PATCH] model: improve get_next_thread() comments It's curious that get_next_thread() needs the current ModelAction as a parameter. It helps to clarify that this argument is somwhat "optional." --- model.cc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/model.cc b/model.cc index 2c0ec9ba..655c511d 100644 --- a/model.cc +++ b/model.cc @@ -214,8 +214,9 @@ Node * ModelChecker::get_curr_node() const * when exploring a new execution ordering), in which case we defer to the * scheduler. * - * @param curr The current ModelAction. This action might guide the choice of - * next thread. + * @param curr Optional: The current ModelAction. Only used if non-NULL and it + * might guide the choice of next thread (i.e., THREAD_CREATE should be + * followed by THREAD_START, or ATOMIC_RMWR followed by ATOMIC_{RMW,RMWC}) * @return The next chosen thread to run, if any exist. Or else if no threads * remain to be executed, return NULL. */ -- 2.34.1