Jim Lawrence
accessd at shaw.ca
Wed Jun 24 13:27:40 CDT 2009
Yes you are right Charlotte, as we are now in the 21st century... Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Wednesday, June 24, 2009 7:36 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Learning .Net -- PHP Instead? 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 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo Sent: Tuesday, June 23, 2009 3:05 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Learning .Net -- PHP Instead? That is what I was saying, Jim. I use GOTO to go to the exitpoint. Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: 23 June 2009 23:01 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Learning .Net -- PHP Instead? Hi John: In light of using GOTO and GOSUB functions RETURN seemed less onerous... Yes, one exit point is the optimum. I try to keep my classes or function small so there is never a reason for even considering more than one exit point. (Big complex procedures are hard to follow... so I try and keep it very simple... one thought one function.) Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, June 23, 2009 1:54 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Learning .Net -- PHP Instead? > You can always just use the Return statement. THAT is bad programming style. You should ALWAYS exit through a common exit point so that cleanup code can execute. John W. Colby www.ColbyConsulting.com Jim Lawrence wrote: > Hi Max: > > Edsger Dijkstra one of the fathers of programming, was credited with > eliminating the GOTO and GOSUB use as just bad programming. ;-) > > http://www.creativesystemdesigns.com/projects/relational.asp#edsger > > You can always just use the Return statement. If you functions are > large enough to require lots of conditional statement maybe it is time > to start splitting up your code blocks. There was an excellent article > that Shamil introduced on the subject of coding methods... but I can > not find the link again. (Age related I suspect) > > Jim > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo > Sent: Tuesday, June 23, 2009 8:31 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Learning .Net -- PHP Instead? > > I use GOTO all the time, as in.. > > If <condition> then > Do something > Goto exithere > Endif > Code > Code > Exithere: > Wind up and exit > Errhandler: > Etc > > Much easier to read then.. > > If <condition> then > Do something > Else > Do something else which is the main coding and stretched on and on. > Endif > > > Dont much care about standards, care more about what works for me... > > Max > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte > Foust > Sent: 23 June 2009 16:03 > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Learning .Net -- PHP Instead? > > There are always nostalga buffs out there ... LOL > > Charlotte > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim > Lawrence > Sent: Monday, June 22, 2009 10:06 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Learning .Net -- PHP Instead? > > I thought GOTO and GOSUB functions were a thing of the past. |-P > > Jim > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Eric Barro > Sent: Monday, June 22, 2009 7:17 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Learning .Net -- PHP Instead? > > Quite frankly I don't see the addition of a GOTO feature to be > something to look forward to in any programming language. > > -----Original Message----- > > > On Mon, Jun 22, 2009 at 12:37 PM, Kenneth Ismert <kismert at gmail.com> > wrote: > >> If you are interested in Web programming, I would suggest PHP. Per >> unit of effort, I think most VBA programmers would get further with >> PHP than with ASPX, especially if you are starting out from scratch. >> > <snipped the rest> > >> Python or Ruby, and make it a much more expressive language than VBA. >> * There is an enormous ecosystem of open-source libraries, IDEs, CMS >> sytems, and MVC frameworks to choose from. >> * Projects developed under Windows/IIS should work with little or no >> changes under Linux/Apache. >> >> PHP Drawbacks: >> >> * PHP is a web-specific language. If you want something >> general-purpose, use something else. >> * PHP's libraries are extensive and rapidly improving, but it doesn't >> have the monolithic library integration that .NET enjoys with the CLR. >> * Comprehensive, transparent support for Unicode is still lacking, as >> it is with most scripting languages. PHP 6 will rectify this. >> >> -Ken >> aseadvisors.com <http://www.databaseadvisors.com> >> > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com