Stuart McLachlan
stuart at lexacorp.com.pg
Wed Jul 3 18:11:53 CDT 2013
Correction: I haven't actually used a GOTO, other than in ON ERROR GOTO, for ... :-) -- Stuart On 3 Jul 2013 at 15:30, David McAfee wrote: > On Error GoTo MyProcedure_Error ;) > > > > On Wed, Jul 3, 2013 at 3:24 PM, Stuart McLachlan <stuart at lexacorp.com.pg>wrote: > > > Agree, what is the "danger of globals" if you: > > > > a. identify them properly using a naming convention > > b. use them properly by only writing them in one location and > > c. trap errors properly. > > > > Same with Goto. It's a perfectly valid command which does exactly the > > same as the heavily > > used assembler JMP,JNE etc instructions. > > > > It's "abuse", not "use" that have given these two their bad reputations. > > > > (But I haven't actually used a GOTO for many, many years - I've never > > found a situation yet > > where there wasn't a "more elegant" solution <g>) > > > > -- > > Stuart > > > > On 3 Jul 2013 at 9:04, Jim Dettman wrote: > > > > > <<And don't get me started on the danger of globals.>> > > > > > > I've used globals since day 1 with Access; have never had a problem. > > > > > > It's sloppy programmers that write sloppy code that's the issue. > > There's > > > nothing inherently wrong with globals from my viewpoint. They serve a > > > purpose and like anything they work fine when used properly. > > > > > > It's like the age old admonishment never to use a goto statement. You > > > can use goto to your hearts content and still maintain well structured > > code. > > > It's a sloppy programmer that ends up with spaghetti code. > > > > > > Jim. > > > > > > > -- > > 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 >