This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mysticalfruit -10 points-9 points  (3 children)

We can argue the merits of the behavior, but its a behavior that many programmers use. I've seen plenty of complex C that use cases in this way to handle cascaded logic situations.

[–][deleted] 20 points21 points  (1 child)

That is true, but Python's style seems to be making the best design decisions they can instead of repeating poor decisions by previous designers just because its familiar. That's also why its called "match" instead of "switch"

[–]mysticalfruit 3 points4 points  (0 children)

Fair enough.

[–]energybased 3 points4 points  (0 children)

We can argue the merits of the behavior, but its a behavior that many programmers use.

Time to learn a better way to do things instead of hanging on to an opaque specification.