I know you can't please everyone in this area, but I thought I would let you know
our naming policy:
1. JavaBean naming conventions (public getter and setter methods) supersede the
following.
2. names of private members (both fields and methods) begin with an underscore.
3. names of non-private instance members (both fields and methods) begin with a
lowercase class abbreviation.
4. names of non-private static members (both fields and methods) begin with an
uppercase class abbreviation since static names are upper case.
5. Parameters and Local Variables do not have global prefixes.
This allows us to visually detect:
* what is visible only inside a method (parameters and local variables have no
prefix)
* what is visible only inside a class (private members begin with underscore)
* what is visible outside a class (non-private members begin with class
prefix)
* what is static (upper case, but also with prefix if non-private)
I would like to be able to use your name prefix facility, but it doesn't quite
map into our naming conventions. What is needed is the ability to specify:
* public JavaBean property accessor methods
* private/non-private attribute
* instance/static attribute
Maybe you have have four generic prefix fields that have selectable attributes
next to them. Our naming conventions could then be implemented like this while
preserving the ability to maintain the exiting prefixes:
Method* Field Parameter LocalVariable | private static
prefix1: [_ ] [x] [x] [ ] [ ] | [x] [ ]
prefix2: [my_ ] [x] [x] [ ] [ ] | [ ] [ ]
prefix3: [MY_ ] [x] [x] [ ] [ ] | [ ] [x]
prefix4: [ ] [ ] [ ] [ ] [ ] | [ ] [ ]
*Do Not Apply to JavaBean Property Accessors (getters and setters): [x]
It would also be nice to have an option in the code reformatting dialog to apply
name prefixes.
cc
_______________________________________________
Eap-list mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-list
