»

[hellcat]

Da hat Mr. Millsap eine starke ausdrucksweise betreffend der Namensgebung von Objekten.

People who, after the sermon, insist upon continuing to embed type information into the names of things are of course free to do so. However, I am also free to fantasize that the grammar police will make these people use their own naming convention at home until they see how ridiculous it is. The parents of Billy the Kid, Attila the Hun, Winnie the Pooh, and Frosty the Snowman were evidently afflicted with such a curse.

;-)

Und ich stimme, mit ganz wenigen Ausnahmefaellen, ueberein.
Es macht schlicht weg keinen Sinn pre/post-fix typisierungs Definitionen in eine Namenskonvention zu packen. Ausserdem ist es gem. meiner Erfahrung schwierig diese Projekt/Firma weit durchzusetzen und Inkonsistenzen zu vermeiden. Insbesondere in Umgebungen mit ineffektiver QA. Also Ueberlasse ich die Namensgebung dem cleveren Entwickler der einen bedeutungsvollen Namen fuer das Objekt findet...
Der benennt dann eine Klasse "Customer" mit einer Methode (Funktion) "getLastName" und nicht "ClCustData" mit "f_lstName".

[netpython]

Die einzigen Conventions, die ich anwende (und meines Erachtens auch sinnvoll sind), habe ich für euch nachstehend referenziert:

Code Conventions for the Java Programming Language

This Code Conventions for the Java Programming Language document contains the standard conventions that we at Sun follow and recommend that others follow. It covers filenames, file organization, indentation, comments, declarations, statements, white space, naming conventions, programming practices and includes a code example.

Design Guidelines for Developing Class Libraries (Microsoft Visual Studio 2005/.NET Framework 2.0)

The design guidelines for developing class libraries are for library development that extends and interacts with the .NET Framework. The goal of the .NET Framework design guidelines is to help library designers ensure that their users reap the benefits of API consistency and ease of use by providing a unified programming model that is independent of the programming language used for development. It is strongly recommended that you follow these design guidelines when developing classes and components that extend the .NET Framework. Inconsistent library design adversely affects developer productivity and discourages adoption.

Common Language Specification (Microsoft Visual Studio 2005/.NET Framework 2.0)

To fully interact with other objects regardless of the language they were implemented in, objects must expose to callers only those features that are common to all the languages they must interoperate with. For this reason, the Common Language Specification (CLS), which is a set of basic language features needed by many applications, has been defined.