Shamil Salakhetdinov
shamil at smsconsulting.spb.ru
Wed Jun 24 10:33:47 CDT 2009
Hi Arthur and Charlotte, I used to use the same "one exit point" principle over the years (especially in my VBA programming) but I must note it's becoming obsolete nowadays: I do not use it almost at all anymore in my C#/VB.NET development. Have a look what is the reasoning behind this "new approach" to not bother about "one exit point" principle: http://ubuntuforums.org/showthread.php?t=631745 http://discuss.joelonsoftware.com/default.asp?joel.3.325456.34 Everything seems to be changing in programming these days but one who has been in programming for some time can rather clearly see we're "just" getting repeating/rethinking of "good old habits" but on higher current level of evolution spiral of computer science, programming methods and practices... Thank you. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Wednesday, June 24, 2009 6:43 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Learning .Net -- PHP Instead? Yup. Over the years I have learned to accept this wisdom: each procedure or function should have exactly one exit point. Define the result variable and set it within your case statement, then jump out and return the result variable. No headaches or scratched foreheads that way. A. On Wed, Jun 24, 2009 at 10:35 AM, Charlotte Foust < cfoust at infostatsystems.com> wrote: > Structured programming suggests you instead design the code so there is > no reason to use a GOTO. If you hit a condition in a particular branch, > the code naturally arrives at the exitpoint. Very clean concept, that. > > Charlotte Foust > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4184 (20090624) __________ The message was checked by ESET NOD32 Antivirus. http://www.esetnod32.ru __________ Information from ESET NOD32 Antivirus, version of virus signature database 4184 (20090624) __________ The message was checked by ESET NOD32 Antivirus. http://www.esetnod32.ru