Scott Marcus
marcus at tsstech.com
Wed Aug 11 14:35:34 CDT 2004
Drew, Why do you take the extreme point of view like this? The name you gave the variable implies that I'm to lazy to read code, can't interpret logic, and that I write extremely long variable names. None of which is true. I don't care how the compiler interprets my variable name, I care how those who maintain my code (including me) interprets it's purpose. I think this is hitting a little too close to home for you. It is true that I want to impress the client in a positive way. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of DWUTKA at marlow.com Sent: Tuesday, August 10, 2004 5:16 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Naming Conventions Actually, I find it easier to remember that I'm using i, then it is to remember that I am using lngSomeLongDrawnOutCompletelyMeaninglessToTheCompilerNameSoThatSomeoneWhoIsT ooLazyToReadTheCodeLogicCanImpressAClientThatTheyKnowAParticularVariableRepr esentsXYZ Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Scott Marcus Sent: Tuesday, August 10, 2004 6:12 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Naming Conventions There are plenty of other things that I would rather fill my mind with when developing and debugging code than remembering in each line of code(in the loop) that 'i' is the employee type and 'j' is the employee counter. Wouldn't you agree that it is hard enough sometimes just to follow the logic of the code you are working on let alone remembering these variable interpretations? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins Sent: Monday, August 09, 2004 9:39 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Naming Conventions Just a slight aside here, but you're gonna have to read the rest of the statement anyway -- if you're counting something, you still need the rest of the statement to figure out the rest -- the variable name itself is NOT going to give you all the information you need. You still need the rest of the statement. Not a for or an against, just thought I'd mention it... Susan H. Even 'intI' means little more than 'i'. Like you said, something like 'intEmployeeCounter' is easy to understand. Just to be even more clear, take the following into consideration... -- _______________________________________________ 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