The most important thing is to find a way of doing things and be consistant. If you work for a company, it might be a good idea to create a style guide for code in the company. Studies have actually shown that consistantly formatted code makes it easier to understand. So going back to code you wrote 6 months ago will be easier to understand just by how it looks.
A great book that taught me a lot about code formatting considerations, as well as a number of other things that don't get talked about much in how-tos, is Code Complete by Steve McConnell. --- In [email protected], "Mike Anderson" <[EMAIL PROTECTED]> wrote: > > Greetings All, > > Whenever I study code generated by seasoned programmers (i.e. all the > Adobe people supporting Flex on this list) as well as countless others > on this list, I notice that some use "this" when referencing local > variables contained within a Class. > > The last thing I want to do here, is start a heated discussion regarding > "best practices" for programming. My goal on a daily basis, is to > better myself as a programmer, and I want to make sure that the code I > create, conforms to certain standards. > > Could some of you please offer your 2 Cents regarding the > advantages/disadvantages of using "this"? Just a quick example: > > package > { > public class myClass() > { > private var testVar:String; > > public function myClass( value:String ) > { > this.testVar = value; > // versus: > testVar = value; > } > } > } > > Thank you all so much in advance, for any help you can offer regarding > this topic. > > Mike >
