<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Code quality issue in weston?" href="https://bugs.freedesktop.org/show_bug.cgi?id=67620#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Code quality issue in weston?" href="https://bugs.freedesktop.org/show_bug.cgi?id=67620">bug 67620</a> from <a class="email" href="mailto:axuv49@hotmail.co.uk" title="J <axuv49@hotmail.co.uk>"> J</a> <pre>While usage of 'goto' constantly receives a lot of negative press, it's usage in C code for error handling is generally considered cleaner than alternatives. In my personal opinion, I find it easier to read as well - rather than multiple levels of scope/indentation based on every potential error, you get a normal flow of code, where the (rare) errors cause the flow to break. If they require the same cleanup code, we sure don't want any duplication either. It's use should still be limited to specific applicable scenarios, but it's not a 'use a single goto and you'll cause a nuclear war' level style of issue. Hell, using a break in a switch statement is essentially a goto itself(!)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>