For such coding standards, 'better' is often very subjective.

Rather, learn from what various project guidelines say, especially if they provide a reason for it. Then decide on what you want, and be consistent about it. Of course, if you're contributing to a project then you should follow the guidelines of that project.

    The first one is just specific to writing pear extensions, although a lot of the things they talk about are good for coding in general. My teachers have usually taught me to just be consistent with your style, use good indentation and name variables meaningfully. As long as you can read it well later on thats good.
    Sometimes if you work for a company they will have their own outline of standards you must follow so everyones code is similar, otherwise read over both of those and mix and match what you like the best,,,in my opinion.

      Write a Reply...