Code Conventions for the JavaTM Programming Language hao,
The cholo
(friend or
) writes: "Cholo a question, a place to give tips to program ... For example, the code commenting. Identify variables for function ... stuff ... You have a post out there on hand ?¡¡?"
I respond to cholo "cholo YYU got me lol ... kicking up history I know that he had seen a doc. Containing a conventions and standards for programming, from A to Z, the best practice when xD throwing code, java course, but applicable to any other language, after 1 hour of exhaustive search I realized 2 things:
- To find things on the record with chrome one dies of hunger, should have an advanced search, to filter by date at least. Or you have not learned to use: S
- When one comes across important information that can not or will not read at the time, but he knows it will be useless, nothing better than to make specific reference somewhere in where we have interesting stuff pending review.
Finally, "ak ta":
Code Conventions for the JavaTM Programming Language With this short doc. we moved in time, in the early school years, when the teacher told us:
- 5 pts. least not let the beginning of the paragraph indentation.
- 5 pts. least not to place capital after the dot.
- 5 pts. least ... So just that you remember, xD Hehehe
you'll see ... "
And it was ... and now I share this
Rueda .
This document contains conventions and standards Sun follows and recommended that we follow. Covers: filenames, file organization, comments, statements, judgments, white space, naming conventions, programming practices and includes sample code. Why coding conventions? - 80% of the cost of a piece of software goes to maintenance. (Do not believe everything perfect the first).
- Most of the software is maintained throughout his life, the original author. (Or will you let someone else make your creation fiesta xD).
- help Code conventions improve the readability of the software, allowing engineers to understand the code faster and further. (Unless you have a virtual machine installed in our brains ready to compile code juju obfuscated).
- If your source is a product (what you're selling or sharing), it is necessary to ensure that clear and clean, like any other product that you would want.
This doc. is perfect to perfect the "estilacho" when "throw code," but if some of us have a buddy who was inspired by "pulling obfuscated code, as pitch and Adrian (
friends or ), we recommend the entire book taca The Java Language Specification
, hehe teased.
The doc. pendejo above is by the book says: If you want to know the Meaning of the language stating's constructs, this is the source for you. Uff who said fear. Well boys enjoy.
May the force be with you! ;)