Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Multiple return points - is it OK practice?
Message
From
01/02/2013 13:56:07
Mike Yearwood
Toronto, Ontario, Canada
 
General information
Forum:
ASP.NET
Category:
Coding, syntax and commands
Environment versions
Environment:
C# 4.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01564936
Message ID:
01564947
Views:
80
This message has been marked as a message which has helped to the initial question of the thread.
>Hi everybody,
>
>I am wondering what are good ways of avoiding multiple return points and yet not being caught in multiple if /else complex logic.
>
>Is it OK to return early? I think in C# it's a normal practice, but what if I need to format output? E.g. at the bottom of each method I have
>
>String returnMessage = Base.GetReturnString(errorValue, statusCode, messageText);
>            Logging.Log("Returning " + returnMessage, 2);
>
>            return returnMessage;
>
>So, should I put these 3 lines in its own method and just do
>
>return LogAndReturn(errorValue, statusCode, messageText);
>
>every time I need to exit the procedure earlier?

If your code checks for a bunch of conditions at the start and exits early when one of them fails, that makes the real heart of the code easier to follow. No need to artificially indent the heart of the code.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform