That works too. It’s up to the submitter’s preference.
I prefer to “fail early” with individual conditions per line of code:
IF condition1 return;
IF NOT condition2 return;
.... all other failure modes listed
DO THESE ACTIONS -- since all other conditions/tests have "passed"
The reason is that each condition can be added/removed/commented out separately; the only conditional action taken is to RETURN; and no need to use BEGIN…END constructs. This leads to greater consistency.
I’ve found that “affirmative” conditions tend to get more elaborate with AND and OR conditions, and mixing those without proper parentheses groups leads to logic errors. It’s better IMHO to indicate which conditions are failure modes so that they are documented in code, and are often simpler than affirmative conditions.
This also helps with unit testing to provide failing test modes, RETURN can be replaced with some kind of assertion.