[9rx]

Neither exceptions, the concept, nor exceptions, the data structure, have anything to do with control flow. You could be thinking of exception handlers, which refers to a control flow mechanism, but if you were you'd be going completely off the rails.

[tcfhgj]

Do you doubt you can use exceptions for control flow? Of course you need to combine with exception handlers.

It's the only use of exceptions not implying a bug

[9rx]

> Do you doubt you can use exceptions for control flow?

The same way you can use bugs for control flow, I suppose, given that bugs and exceptions are different categories within the same general idea of programmer mistakes. With bugs, of course, being mistakes around "business" rules, and exceptions being mistakes made around computing environment rules.

> Of course you need to combine with exception handlers.

How do you combine a programmer making a mistake with exception handlers? Exception handlers only exist inside programming languages. Are you under the impression that programmers also live inside programming languages? That's... interesting.

[tcfhgj]

> With bugs, of course, being mistakes around "business" rules, and exceptions being mistakes made around computing environment rules.

For me, bugs are all mistakes which manifest themselves in software misbehaving. Maybe it surfaces by a program crash of an uncaught exception or an error message presented to the user, a program termination, a wrong result, ...

> How do you combine a programmer making a mistake with exception handlers?

I write a bug leading to an exception sometimes and catch the exception, then try the operation again, or show an error to the user

[9rx]

> For me, bugs are all mistakes which manifest themselves in software misbehaving.

And that's fine. It is not like there is some magical deity in the sky that creates and enforces the law of language. Words are just made up by humans on a whim. If I want to exert my own whim and call that "zigglefritz" instead, that works too.