On Apr 06, 2007, at 18:08 UTC, Tim Hare wrote: > My personal opinion is declare the variable at the beginning of the > *scope* of where it is needed. If you declare it immediately before > its first use, then you have to really hunt to find the definitions > of variables that are randomly sprinkled through the code.
Under what circumstances do you find a need to do that? I'm trying to think of a case, but it just doesn't seem to come up for me. If I want to know what type a variable is, I just mouse or cursor over it and the status line tells me. It also tells me where it's defined, for that matter -- but the way I work, that's almost always within the last few lines, so I don't often find myself wondering. However, this does bring up an interesting feature idea. We already have "Go To Window1.Foo" in the contextual menu for a variable Foo defined as a property of Window1. But for a local variable, the contextual menu has no such entry. It could have a "Go To Definition" command that would just jump to the line where that variable is defined (clearly the IDE knows where that is since it tells you in the status bar). A small thing, but it might be handy now and then. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
