Comment by stouset
2 hours ago
> where I need to make sure certain functions are called in order
The ticket approach is a neat way to handle this, but I’ve always felt that functions needing to be called in a specific order is usually a bad code smell.
I’m sure there are times it’s unavoidable or maybe even the cleanest approach, but I don’t think I’ve encountered one in my career. When are you finding you need to do this?
Making sure something can be only used correctly is bad? Why?
> I’ve always felt that functions needing to be called in a specific order is usually a bad code smell
Can you give an example where a different design eliminates the need for the ticket pattern?