Difference between revisions of "Style Guidelines"

m
Line 1: Line 1:
 
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.
 
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 ==
+
==Status of this page==
Feature clause names, well know names.
+
[[User:Bertrand Meyer|Bertrand Meyer]] 12:35, 22 May 2008 (PDT)I am starting this page by copy-pasting from existing references. It will be edited and cleaned up later on.[[User:Bertrand Meyer|Bertrand Meyer]] 12:35, 22 May 2008 (PDT)
 
+
== 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 11:35, 22 May 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.

Status of this page

Bertrand Meyer 12:35, 22 May 2008 (PDT)I am starting this page by copy-pasting from existing references. It will be edited and cleaned up later on.Bertrand Meyer 12:35, 22 May 2008 (PDT)