X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/7672ae43c2b49a7dcdc0976cc89a05cc87ae534c..40ee10e13b61bfb28374d96ade010a262b5abd44:/include/simgrid/simix.hpp diff --git a/include/simgrid/simix.hpp b/include/simgrid/simix.hpp index ac24d4f820..338c3372ae 100644 --- a/include/simgrid/simix.hpp +++ b/include/simgrid/simix.hpp @@ -1,5 +1,4 @@ -/* Copyright (c) 2007-2022. The SimGrid Team. - * All rights reserved. */ +/* Copyright (c) 2007-2023. The SimGrid Team. All rights reserved. */ /* This program is free software; you can redistribute it and/or modify it * under the terms of the license (GNU LGPL) which comes with this package. */ @@ -62,7 +61,7 @@ template typename std::result_of_t simcall_answered(F&& code, Sim * * Simulation without MC and without parallelism (contexts/nthreads=1) will not pay the price of a simcall for an * harmless setter. When running in parallel, you want your write access to be done in a mutual exclusion way, while the - * getters can still occure out of order. + * getters can still occur out of order. * * When running in MC, you want to make this access visible to the checker. Actually in this case, it's not visible from * the checker (and thus still use a fast track) if the setter is called from the actor that created the object. @@ -83,7 +82,7 @@ template typename std::result_of_t simcall_object_access(ObjectAc /** Execute some code (that does not return immediately) in kernel context * - * This is very similar to simcall() right above, but the calling actor will not get rescheduled until + * This is very similar to simcall_answered() above, but the calling actor will not get rescheduled until * actor->simcall_answer() is called explicitly. * * This is meant for blocking actions. For example, locking a mutex is a blocking simcall. @@ -115,5 +114,4 @@ auto simcall_blocking(F&& code, Observer* observer) -> decltype(observer->get_re return observer->get_result(); } } // namespace simgrid::kernel::actor - #endif