You may not like all rules presented here, but they feed very well for me and vex helped producing high quality code. Everyone is allow go to code however they want, write and follow their bear mien guides, but when you contribute to my code, please follow these rules: == data format: * occasion ASCII (or UTF-8, if you have to). * Use 2 space indent, no tabs. * Use Unix-style place closureings. * Use spaces more or less operators, after commas, colons and semicolons, around { and before }. * No spaces after (, [ and before ], ). * Use devil spaces before teaching modifiers (postfix if/unless/while/until/rescue). * Indent when as ambiguous as case. * Use an abandon line before the furnish apprise of a method (unless it only has one line), and an empty line amongst defs. * Use RDoc and its conventions for API documentation. Dont put an empty line surrounded by the explanation block and the def. * Use empty lin es to break up a long method into logical paragraphs. * Keep lines less than 80 characters. * Avoid trailing whitespace. == Syntax: * Use def with p bentheses when there are arguments. * Never workout for, unless you exactly go through why. * Never wont then. * Use when x; ... for one-line cases. * Use &&/|| for Boolean expressions, and/or for maintain come down.
(Rule of thumb: If you have to use outside parentheses, you are victimization the wrong operators.) * Avoid multiline ?:, use if. * subordinate superfluous parentheses when name methods, but keep them when calling functions, i.e. when you use the g! ift value in the same line. x = Math.sin(y) array.delete e * Prefer {...} over do...end. Multiline {...} is alright: having different statement endings (} for blocks, end for if/while/...) makes it easier to see what ends where. hardly use do...end for control flow and method definitions (e.g. in Rakefiles and accredited DSLs.) Avoid do...end when chaining. * Avoid return where not required. * Avoid...If you want to startle a full essay, couch it on our website: OrderCustomPaper.com
If you want to get a full essay, visit our page: write my paper
No comments:
Post a Comment