Difference between revisions of "PTP/policy/developer guidelines"

From Eclipsepedia

< PTP‎ | policy
Jump to: navigation, search
(Additional requirements for Java source)
(Additional requirements for C source)
Line 82: Line 82:
 
*Start each line of a multiline comment with an '*' aligned with the '*' in the '/*'
 
*Start each line of a multiline comment with an '*' aligned with the '*' in the '/*'
  
Naming conventions for global objects:  
+
Naming conventions:
  
*Capitalize the first letter of each word (e.g.MIBreakpointGetBreakInsertInfo)  
+
*Global function and type identifiers:
*Do not use '_' or '-'  
+
**Capitalize the first letter of each word (e.g.MIBreakpointGetBreakInsertInfo)  
*Use descriptive names
+
**Do not use '_' or '-'  
 
+
**Use descriptive names
Naming conventions for local/utility objects:  
+
*Local (static) and utility function and type identifiers, and structure field identifiers:  
 
+
**All lowercase  
*All lowercase  
+
**Separate words with '_'  
*Separate words with '_'  
+
**Do not use '-'
*Do not use '-'
+
*Local (static) variables:
 +
**Can start with '_'

Revision as of 14:41, 13 November 2010

PTP adheres to the Eclipse Foundation development conventions and guidelines. Please make sure you read through these before committing code (if you're a committer) or submitting code contributions (if not).

The following practices should also be observed:

Contents

Java Errors/Warnings

Developers should override default compiler error/warning and use project specific errors/warnings. These errors should be enabled:

  • Method with a constructor name - Error
  • Non-externalized strings (missing/unused $NON-NLS$ tag) - Warning
  • Assignment has no effect - Error
  • Possible accidental boolean assignment - Error
  • finally does not complete normally - Error
  • Using a char array in string concatenation - Error
  • Null pointer access - Error
  • Potential null pointer access - Warning
  • Unused Import - Error

All committers and contributors submitting patches should enable API tooling by setting target baseline platform. Do not commit code with API errors.

Patches with errors listed above including API errors will not be accepted without corrections.

Additional requirements for Java source

  • Use interfaces as much as possible
  • All interfaces and methods must include a Javadoc comment
  • Interface implementations must include a non-Javadoc comment (using Generate Element Comment)
  • All classes, methods and fields should have an access modifier (public, protected, private)
  • Use the following class, method and field modifier order:
    1. Access modifier
    2. abstract
    3. static
    4. final
    5. transient
    6. volatile
  • All source should be formatted using the "PTP" code formatter profile
  • All members should be cleaned up using the "PTP" profile (Source->Clean Up)
  • Column width should be set to 132

The PTP formatter and clean-up profiles are available here.

Adding new Plugin

  • Add the plugin to the anonymous and committer project sets for HEAD.
  • Add the plugin to a feature so it gets built (in this case it should be org.eclipse.ptp.core-feature)
  • Add the plugin to the map file org.eclipse.releng/maps/ptp.map
  • Add a tagone entry in the tag target in org.eclipse.ptp.releng/build.xml
  • Add a about.html
  • Announce on ptp-dev

There is some documentation on the release engineering here: http://wiki.eclipse.org/PTP/release_engineering

Additional requirements for C source

  • All functions must be commented
  • Only include header files that are explicitly used
  • Always initialize variables before use (including static)
  • Always test explicitly for NULL
  • Always use NULL for pointers, not 0
  • Always test for an explicit value from strcmp

C source formatting guidelines:

  • Function body '{' and '}' on their own line
  • Function type on its own line (including static qualifier)
  • Function arguments separated by one space
  • Functions local to a file should be declared static
  • One variable declaration per line
  • Variable declarations should be followed by a blank line
  • No spaces before or after '(' and ')' in functions
  • Opening brace on same line as last ')' in an if statement expression
  • Space separating 'if' and '('
  • No spaces after '(' or before ')' in if statements
  • No braces around return values
  • Opening brace on same line as 'else'
  • 'else' on same line as '}'
  • Only use '/*' and '*/' for comments
  • Put '/*' and '*/' on their own line for multiline comments
  • Start each line of a multiline comment with an '*' aligned with the '*' in the '/*'

Naming conventions:

  • Global function and type identifiers:
    • Capitalize the first letter of each word (e.g.MIBreakpointGetBreakInsertInfo)
    • Do not use '_' or '-'
    • Use descriptive names
  • Local (static) and utility function and type identifiers, and structure field identifiers:
    • All lowercase
    • Separate words with '_'
    • Do not use '-'
  • Local (static) variables:
    • Can start with '_'