mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DIRMINA-198) Naming conventions
Date Tue, 05 Sep 2006 03:29:23 GMT
     [ http://issues.apache.org/jira/browse/DIRMINA-198?page=all ]

Trustin Lee resolved DIRMINA-198.

    Resolution: Won't Fix
      Assignee: Trustin Lee

I agree with Peter and we're already doing the same for static final members.  Most modern
IDEs are intelligent enough to syntax-highlight the code to distinguish static fields and
non-static fields.

> Naming conventions
> ------------------
>                 Key: DIRMINA-198
>                 URL: http://issues.apache.org/jira/browse/DIRMINA-198
>             Project: Directory MINA
>          Issue Type: Wish
>    Affects Versions: 0.9.3
>            Reporter: Michael Bauroth
>         Assigned To: Trustin Lee
>            Priority: Trivial
> It would be a great idea to define some naming conventions for the source code. Especially
for new users, but also for all others it can be confusing to know, if a special variable
in a longer method is static or global or anything else. Naming conventions can generate more
readable code and a quicker programming progress.
> In our company we use the following conventions:
> static final variables: UPPER_CASE
> static variables: sStatic (leading -s, next letter big)
> global variables: mMember (leading -m, next letter big)
> local (temporary) variables: tTemp (leading -t, next letter big)
> parameters: pParam (leading -p, next letter big)
> What do you think?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message