If I'm programming "on my own" I'll usually adopt the RETURN instead of continuing, just because it's *faster* to not process the rest of the statements that don't need processing. However, I have been told NOT TO DO THAT by someone who was substantially IRKED by multiple returns, and instead adopted the
IF NOT(ERROR) THEN Stuff END IF NOT(ERROR) THEN Stuff END Approach. ERROR being a standard system variable on MT500, M2K's way of passing different ways to abort/handle screen prompt processing scenarios. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Anthony Youngman Sent: Wednesday, November 28, 2007 08:46 To: 'u2-users@listserver.u2ug.org' Subject: RE: [U2] Deep and long indentations vs multiple exit points I must admit I prefer multiple exit points, but I'll throw a third variant into the mix ... OK = TRUE IF OK THEN Various statements that set OK to false if there's an error END IF OK THEN More statements that set OK to false if there's an error END <snip> ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
