>>>>>>>>Hi,
>>>>>>>>
>>>>>>>>>If I'm programming for you and I find it readable the other way, let me code it my way. That is the most productive I can be. Learning to change my practice to suit you slows me down and does not really help you.
>>>>>>>>
>>>>>>>>Hmmm. Given that most replies here preferred the second style: if you were working with them do you really think that overall productivity would be improved if you opted out of the consensus?
>>>>>>>>
>>>>>>>>Have you ever worked for a house that imposes standards?
>>>>>>>>Regards,
>>>>>>>>Viv
>>>>>>>
>>>>>>>Yes. Hated it. One or more Nazis.
>>>>>>I didn't like it either but complete anarchy would have been worse. Twenty guys left to their own devices would come up with twenty different styles.
>>>>>
>>>>>Beautify is your friend!
>>>>You don't know what I look like :-{
>>>
>>>:)
>>>
>>>
>>>>But I was speaking in a more general sense - variable naming and declaration etc...
>>>
>>>That does not fall under "style" in my mind. Variable naming has a direct impact on code behavior - causing or preventing crashes.
>>
>>>White space has an indirect effect.
>>
>>Variable naming has no effect - it's just style. Variable *scoping* OTOH....
>
>Nope. If you name a variable the same as a field name, and you're not using m., it can crash if the data types don't match.

M. is a form of scoping