Charlotte Foust
cfoust at infostatsystems.com
Wed Aug 4 16:37:59 CDT 2004
Inherently? Nothing. But when you have a long routine (yes, I know long routines are bad and I don't build them that way, but I still have to deal with them) that is passing I into another function or doing some math with it, having no clear indication of the datatype in the variable name makes it more likely that you'll have trouble debugging problems that involve that variable. I believe in saving work down the road by taking precautions up front. Like I said, I'm lazy. Charlotte Foust -----Original Message----- From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] Sent: Wednesday, August 04, 2004 1:15 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Naming Conventions What's wrong with: For I=1 to 50 Next I ? Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Wednesday, August 04, 2004 3:22 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Naming Conventions Susan, I hope they do. I had to when I was learning to use a naming convention. It's a rite of passage for developers. One of the things a new developer needs to learn is how to write standardized code that someone else can decipher. Unless they're experienced, their code is going to need a lot of revision over time, and they'll save plenty of time for themselves and others down the road if no one has to struggle to figure out what those objects and variables are. When I have to deal with code that uses variables like i, j, k, l m or objects like ThisOne, ThatOne, TheOther, I want to beat someone to a bloody pulp for winging it. On the other hand, if someone uses prefixes, I may be baffled by a few of them the first time I see them, but it won't take long to learn to translate. Charlotte Foust -----Original Message----- From: Susan Harkins [mailto:ssharkins at bellsouth.net] Sent: Wednesday, August 04, 2004 12:15 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Naming Conventions A good point, Susan. In my case, of course, the answer is ME. ===========I can see a new developer spending more time checking the list of abbreviations than coding. ;) Susan H. -- _______________________________________________ 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