• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            Overview

            Applications on Symbian OS use a standard set of conventions to name their classes, structs, variables, functions, macros, enumerations, and constants. This topic explains the meaning of these conventions.

             

            Class names 

            Most class names are formed with a prefix letter C, T, R, or M. Briefly, the meaning of these is as follows: 

          1. C: heap-allocated classes, that are derived from a base class CBase

          2. T: value classes, that do not own any external object

          3. R: resource classes, that contain handles to a real resource which is maintained elsewhere

          4. M: interface classes, that define abstract protocol definitions that are implemented by derived classes

            Classes that consist solely of static member functions have no prefix letter. Beyond the prefix, the class name is usually a noun that indicates the purpose of the class.


            Struct names

            Structure types are considered as similar to T classes, as they should not own external objects, and are normally given names beginning with T (although some begin with S).


            Variable names

            Member variables names begin with i, e.g. iMember. This makes it easy to check that certain cleanup-related rules are being obeyed. Arguments names begin with a, e.g. aControl or aIndex. Local variables names have no initial letter. Global variables are usually avoided, but when used, their names begin with a capital letter.

            Symbian OS does not use Hungarian or any notation which attempts to include the variable type in its name: such notations are ugly, and become impossible to manage when there are several hundred classes in the system. They are irrelevant anyway: functions are usually so short that it is easy to see the types of variables defined in them, and class browsers provide a quick way to find the types of class members.


            Function names

            Functions names indicate what they do. They are usually verbs. One exception is getter functions: for a function which returns the value of a member variable, the function name is usually the name of the variable, without the leading i:

            inline RWindow& Window() const { return iWindow; };

            A corresponding setter function would include the word Set, e.g. SetWindow().

            To terminate functions because of error conditions, Symbian OS does not use standard C++ exception handling, but its own system called leaving (see Cleanup Support Overview). Any function that might leave has a name ending in ...L(). This makes the fundamental process of checking for errors easier. The new (ELeave) function might also leave. The fundamental leaving function is User::Leave(). Any function that contains any of these, and does not trap them, might itself leave, and should be coded with a trailing L in its name. If a function calls another which might leave, then its name should have the L suffix also.

            Associated with the leaving mechanism, is the cleanup stack, which allows memory allocated on the heap to be recovered when a leave occurs. An allocation or construction function which places data on the cleanup stack ends with ...LC(). For instance, many new, PushL(), ConstructL() sequences are encapsulated in a NewLC() function:

            CS* s=CS::NewLC(p1, p2);

            This allocates the object, initialises it, and leaves it on the cleanup stack. This process may leave (if only through the PushL()!), so such functions always include an L, and are therefore ...LC().

            A function which takes ownership of its object and destroys it has a name ending in ...D(). An example is the UI framework dialog protocol:

            CEikDialog* dialog=new (ELeave) CBossSettingsDialog;
            if (dialog->ExecuteLD(R_BOSS_SETTINGS_DIALOG))
                {
                // handle successful settings
                }

            The ExecuteLD() function includes second-phase construction, execution of the dialog and then destruction.


            Macro names

            Macro names are all capitalised, with underscores to separates words.


            Enumeration names

            Enumerations are named as follows:

            • as enumerations are types, they have the T prefix
            • enumeration members have the prefix E
            • type and members should have a meaningful, unambiguous name

            Enumerations should be scoped within the relevant class, so as not to pollute the global name space.

            An example of the declaration and use of an enumeration is as follows:

            class TDemo
                {
            public:
                enum TShape {EShapeRound, EShapeSquare};
                };

            TDemo::TShape shape=TDemo::EShapeSquare;



            Constant names

            Names of constants have a prefix K. For example,

            const TInt KMaxNameLength=0x20;

          5. Feedback

            # re: Name Conventions for Applications on Symbian OS  回復  更多評論   

            2008-04-27 14:59 by cheney
            支持!

            posts - 1, comments - 5, trackbacks - 0, articles - 2

            Copyright © cheney

            久久www免费人成看片| 久久91精品综合国产首页| 久久久久99这里有精品10 | 亚洲人成网站999久久久综合 | 久久国产精品无| 伊人久久大香线蕉综合影院首页| 久久久久久亚洲AV无码专区| 久久精品这里热有精品| 综合久久精品色| 一本色道久久88加勒比—综合| 一级做a爰片久久毛片免费陪| 久久精品a亚洲国产v高清不卡| 久久99国产精一区二区三区| 伊人色综合久久天天人守人婷| 日韩人妻无码精品久久免费一| 久久97久久97精品免视看秋霞| 亚洲精品国产美女久久久| 亚洲一区二区三区日本久久九| 亚洲综合日韩久久成人AV| 狠狠色综合网站久久久久久久| 久久国产精品99精品国产| 无码任你躁久久久久久老妇| 亚洲午夜久久影院| 国内精品久久久久久野外| 伊人久久大香线蕉综合Av| 久久久久亚洲AV综合波多野结衣| 久久er99热精品一区二区| 亚洲国产天堂久久久久久| 91久久精品电影| 久久香蕉综合色一综合色88| 久久久久久久久久久久中文字幕| 欧美成人免费观看久久| 久久精品无码av| 久久久网中文字幕| 精品久久久久久久久久久久久久久| 精品午夜久久福利大片| 99精品久久精品| 久久综合久久综合九色| 亚洲欧美日韩精品久久| 国产一区二区精品久久岳| 九九久久精品无码专区|