CSC/ECE 517 Fall 2012/ch1 1w23 ph: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== Introduction == | == Introduction == | ||
Ruby Coding Guidelines include best practices followed generally for most of the object oriented programming languages as Ruby is entirely 'Object Oriented'. Designed and developed in the mid-1990s by Yukihiro "Matz" Matsumoto in Japan, Ruby embodies syntax inspired by Perl with Smalltalk-like features and was also influenced by Eiffel and Lisp. | |||
Coding guidelines help develop a strong codebase and also improve the maintainability of applications. Naming conventions, class and member design principles, maintainability, performance, documentation and layout are the important areas where these guidelines have to be followed. | |||
== Importance of guidelines == | == Importance of guidelines == | ||
== Types of Guidelines == | == Types of Guidelines == | ||
Revision as of 23:48, 15 September 2013
Ruby Coding Guidelines
Introduction
Ruby Coding Guidelines include best practices followed generally for most of the object oriented programming languages as Ruby is entirely 'Object Oriented'. Designed and developed in the mid-1990s by Yukihiro "Matz" Matsumoto in Japan, Ruby embodies syntax inspired by Perl with Smalltalk-like features and was also influenced by Eiffel and Lisp.
Coding guidelines help develop a strong codebase and also improve the maintainability of applications. Naming conventions, class and member design principles, maintainability, performance, documentation and layout are the important areas where these guidelines have to be followed.