| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (5 out of 6)

Using Naming Conventions for Items and Attributes

To help you develop and maintain your application, we recommend that you use standard naming conventions to represent classes and instances in G2. In particular, you should give a great deal of thought to public class and attribute names, because once your software is in use, it is difficult to change the names later.

Follow these guidelines when choosing names for items and attributes:

Make class and attribute names as descriptive as possible and do not use abbreviations. This naming convention supports self-documenting code and maintainability.
Represent class and attribute names as hyphenated words, for example, gfr-local-text-resource.
Using module prefixes
Use public and private naming conventions

For more information, see the references in this table:

For information on... See...
Module prefixes
Using Module Prefixes

Public and private naming conventions
Using Public and Private Naming Conventions

| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (5 out of 6)

Copyright © 1997 Gensym Corporation, Inc.