It's not for variable names, it's for properties and methods. I have to refactor code all the time - I'm not smart enough to get it right the first time.
When you think about it, it's really just a nature extension to typeof. We don't hard code type names, so why hard code member names? -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of silky Sent: Wednesday, May 26, 2010 4:59 PM To: ozDotNet Subject: Re: ASP.NET Control databinding, member properties, dynamically fetch property name? On Thu, May 27, 2010 at 1:51 AM, David Kean <david.k...@microsoft.com> wrote: > I'm really interesting in hearing why people think this is a bad idea. > I've done this in a few code bases (not ASP.NET, but WinForms) and it > nothing but pure goodness from my perspective. Why do you do it? Is it only for the refactoring? Why are you changing variable names that much? Maybe it's just me, but I rarely change any variable name. -- silky http://www.programmingbranch.com/
