On Wed, Sep 17, 2008 at 1:24 PM, Nolan Erck <[EMAIL PROTECTED]> wrote:
> If I have to deal with files that are incredibly long, I may not see the
> initial (for example) CFQuery, or ArrayNew() or other "clue" as to what the
> data type is.  Without scrolling up to the top of the screen (and losing my
> place), I may have no idea what "foo" is storing (okay, I may have SOME
> idea, but I'm still having to do a bit of guess work).

That's a bigger problem with code quality! You're using HN as a way to
mitigate poor code structure instead of doing the "right" thing to
restructure the code (I know, not always possible if you inherit
spaghetti code).

If you have modular code with clear English-like variable and function
names, this "lost in the forest" problem simply doesn't come up.

> Quick! What's the variable "User" storing? An object? A struct? A string?
> There's no way to tell without looking at other code.  Now, what's "strUser"
> storing?

In my code, user is always storing an instance of some User class and
userId is always storing the PK of such an object. Again, if you write
clean OO code, the "what type is it?" question almost never comes up.

> (Joelonsoftware.com has a great article on naming conventions, prefixing
> variables based on if they're safe (i.e. the data has been tested), or
> unsafe (just submitted by an unknown user via a web form) and so on.  It's
> well worth reading.)

And that is much closer to what Simonyi had in mind with his semantic prefixes.
-- 
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to