Setting a Breakpoint on an Exit Statement- Delphi 239

[@pmcgee003]

I'd argue that, especially in this case, it'd be more logical and pleasingly symmetric code to use exit(string result) on every line, and delete the empty result initialisation. 🙂 If the code changes, the compiler should warn us (I think) if we might be exiting without assigning a return value.

[@aarondcmedia9585]

For youtube search results, do you think "Setting a breakpoint on an exit statement" would be more successful as a video title?

[@Graham_Wideman]

I agree -- this video is not about "you" nor "stopping", it's about the debugger breaking. The current title sounds more like advice about driving your car on the motorway! Nonetheless a useful tip.

[@codegearguru]

Done. Thanks. I don't always get to spend much time thinking about a title, or description. It's about having a window of time to record something, and getting it all done. I did make a thumbnail though, so progress?

[@aarondcmedia9585]

@@codegearguru good progress!

[@exeware]

It doesn't breakpoint because it's a compiler optimization, if you start using exit(0) just to be able to stop you're missing a good optimization.

[@codegearguru]

Certainly if it's something that's being called extremely frequently, but these days, I go for maintainability just about every time.

[@trnod]

Just put a comment behind the Exit; where you threatens to start using C++ instead... That will make the compiler step up its game...