Difference between revisions of "Style Guidelines"
(Initial page for style guidelines) |
m |
||
| Line 1: | Line 1: | ||
| − | Style Guidelines that EiffelStudio developers should use. | + | Style Guidelines that EiffelStudio developers should use and are not intended or suggestions for developing code with the Eiffel language. The guidelines are to promote consistency in API design, making EiffelStudio's code base more readable to all. |
| + | |||
| + | == Feature Categorization == | ||
| + | Feature clause names, well know names. | ||
| + | |||
| + | == Commenting == | ||
| + | |||
| + | == Boolean Status Functions == | ||
| + | There are a number of camps when it comes to Boolean functions, reporting class' status. To use 'is_' (and other forms of) or not to? | ||
Revision as of 06:35, 18 March 2008
Style Guidelines that EiffelStudio developers should use and are not intended or suggestions for developing code with the Eiffel language. The guidelines are to promote consistency in API design, making EiffelStudio's code base more readable to all.
Feature Categorization
Feature clause names, well know names.
Commenting
Boolean Status Functions
There are a number of camps when it comes to Boolean functions, reporting class' status. To use 'is_' (and other forms of) or not to?
