[AccessD] Naming Conventions

LOL, yep, it generally does go back to "I'm old and set in my ways and
that's the way I want to do it".  Believe me, I use that a lot these days.

John W. Colby
www.ColbyConsulting.com 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim
Sent: Monday, August 09, 2004 12:31 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


We should definitely eschew obfuscation! The main reason I using naming
conventions is I hate running across old unreadable code and realizing I was
the idiot who wrote it :-(. On the other hand, the only way I will give up
my x, y and i counters is when they pry them from my cold, dead hands <g>.
These are my last links with days of old when real men programmed in
assembler, Fortran was cutting edge, etc., etc. This recalls a discussion
sometime ago when one of our younger cohorts asked what was wrong with
generating an error to test for a condition in code such as

On Error Resume Next
Set appExcel = GetObject(, "Excel.Application") Excel_is_running =
(Err.Number = 0)

The answer is nothing is wrong but I shuttered nonetheless. I avoid code
like that and I guess it goes back to the FORTRAN days when one itty bitty
error would generate pages of error codes <shutter again>. Hey, we can't
deny our roots.  If you want my rationalization 
a) my loops are short enough that the meaning of the counter is
intrinsically obvious to the casual observer and
b) I find array(x,y) easier to follow and read than
array(somehumongousmultidimensionalname,yetanotherincrediblyingenious name)
in fun, Jim Hale

-----Original Message-----
From: Colby, John [mailto:JColby at dispec.com]
Sent: Monday, August 09, 2004 10:49 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


Counters count SOMETHING.  What is it counting?  WHY are you bothering to
count?  

It is exactly that thinking that leads to obfuscation.

JWC