Rename timer `Setup` function to `Schedule`
This patch was motivated by my desire to fix a typo in the function
name. The noun "setup" is 1 word. The verb "set up" is 2 words. All
other member functions are verbs, so this one should be a verb too.
That means that the function should be called `SetUp`. During the
discussion that resulted from the rename, James Kuszmaul pointed out
that "setting up" a timer can be confusing. It implies that you can
only "set up" a timer once. But the intent is to let users set up
timers as many times as they like. So we decided on renaming the
function to `Schedule`. That conveys the purpose and intent better.
I took this opportunity to fix some other typos involving the verb
"set up".
Signed-off-by: Philipp Schrader <philipp.schrader@gmail.com>
Change-Id: I2f557d1f946960af82711f248820d5e2d385a5d3
diff --git a/aos/aos_send.cc b/aos/aos_send.cc
index 210a2af..980ebc7 100644
--- a/aos/aos_send.cc
+++ b/aos/aos_send.cc
@@ -67,9 +67,9 @@
->AddTimer([&fbb, &sender]() {
sender->CheckOk(sender->Send(fbb.GetBufferPointer(), fbb.GetSize()));
})
- ->Setup(cli_info.event_loop->monotonic_now(),
- std::chrono::duration_cast<std::chrono::nanoseconds>(
- std::chrono::duration<double>(1.0 / FLAGS_rate)));
+ ->Schedule(cli_info.event_loop->monotonic_now(),
+ std::chrono::duration_cast<std::chrono::nanoseconds>(
+ std::chrono::duration<double>(1.0 / FLAGS_rate)));
cli_info.event_loop->Run();
}