[AccessD] 16 bit Integer bad practice

Who ever said that "THAT" was good programing practice?

if you dim someting as LONG, it may be efficient to name the variable as 
lngSomeVariable, tho that is not required, what IS a better programming 
practice is consistency, diming something as INTEGER but naming it as lng is 
straight out of the "how to write unmaintainable code". And for the sake of 
this thread, neither brings anything new to the discussion, rather it makes 
your argument NULL.


On 5/18/05, DWUTKA at marlow.com <DWUTKA at marlow.com> wrote:
> 
> I did. See my comment on your code...then look at your code...then try to
> remember that big long speech about how important
> it is to use proper prefixes...because as we all know, our compilers and
> intepreters all know that when you type dim lngAdd As Integer, that it is
> SUPPOSED to see your prefix, not your declaration! <evilgrin>
> 
> Really JC, if you are going to keep picking on me with this Jedi
> stuff....make sure you at least know how to use the force. <grin>
> 
> Drew
> -----Original Message-----
> From: John W. Colby [mailto:jwcolby at colbyconsulting.com]
> Sent: Wednesday, May 18, 2005 1:03 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] 16 bit Integer bad practice
> 
> And in fact, it doesn't even make them slower. See my timing results 
> email.
> 
> John W. Colby
> www.ColbyConsulting.com <http://www.ColbyConsulting.com>


-- 
-Francisco
http://pcthis.blogspot.com |PC news with out the jargon!
http://sqlthis.blogspot.com | Tsql and More...