<leftylink>
though I would note that most times I would just store my state and have another handler do things when receive the message
<leftylink>
rather than block a thread for a long time
<dominikh>
yeah, with Cinch, it's essentially a lot of callback and per-user state. one of its design flaws
<CM-Punk>
leftylink, what I was hoping to do was do like a "first run wizard" and have the bot say something like "What is your password?"
<CM-Punk>
After you type !FirstRun
<dominikh>
but yeah, what you want is a simple state machine for each user
<CM-Punk>
Then it will wait....until the password is given
<dominikh>
really not that difficult. record in which state a user is, see if a command is valid to change to another state
<dominikh>
and each command is a method/handler
<CM-Punk>
Okay, I'll have to do some research into that because I didn't understand most of that.
<leftylink>
well from your point of view, all you care about is... when I trigger the first run, I move to step 1 of the setup and you send me the corresponding message. when I provide my password, the bot proceeds with step 2. well ok, so in the context of what has been discussed here... when I give you my password, am I on step 1? if so, great proceed to step 2, otherwise do nothing
<leftylink>
the condition variable could work and it's be interesting to keep the entire flow in one method, but not strictly necessary
<dominikh>
also, considering how easy it is to get CVs wrong…
<leftylink>
that's an interesting question because I took a class that went to great pains to tell us bout semaphores and condition variables, but I have not used them too much and meanwhile languages are moving toward other paradigms
<CM-Punk>
leftylink is right
<dominikh>
leftylink: won't get around learning semaphores, but yeah, CVs are less interesting with other paradigms
<leftylink>
like go building in channels and erlang's had actors for a while. I just feel like that instructor puts in some wasted effort
<CM-Punk>
Triggering first run would move to Step 1 of the Wizard, the Eve-Bot would ask for the password, and then wait for it. When that user messages the bot again, it will record that message as the password and ask the question in Step 2.
postmodern has joined #cinch
<dominikh>
leftylink: well, guess which constructs the people who implement Go and erlang use ;)
<dominikh>
every channel is an implied mutex, e.g.
<dominikh>
s/is/has
<leftylink>
the word is clearly moving in other directions, and I wonder whether the course's instructor will have to update the course material sometime soon
<leftylink>
s/word/world/
<leftylink>
s/other directions/directions other than semaphores and CVs/
<dominikh>
(also, there is a lot of code in Go that is a lot cleaner when using mutexes; and a semaphore implemented with channels is still a semaphore :>)
<dominikh>
he may need to add new stuff, sure, but it's always wrong to stop teaching old methods
<dominikh>
as they're the ones that make machines actually work
<leftylink>
ok, I can see that
<dominikh>
like they do in some courses, where the first thing they teach is Java and nobody even knows what a stack and a heap are