• <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

            久久se精品一区精品二区| 久久亚洲精品成人AV| 久久99精品久久久久久噜噜| 久久亚洲高清观看| 久久国产精品偷99| 欧美精品国产综合久久| 久久精品麻豆日日躁夜夜躁| 99热热久久这里只有精品68| 亚洲国产精品无码久久久秋霞2 | 国产福利电影一区二区三区久久久久成人精品综合 | 婷婷伊人久久大香线蕉AV| 久久99热国产这有精品| 亚洲国产高清精品线久久| 国产综合久久久久久鬼色| 日本国产精品久久| 久久精品成人免费网站| 亚洲精品无码久久久久sm| 999久久久免费国产精品播放| 久久久久久精品成人免费图片| 91久久精品无码一区二区毛片| 国产偷久久久精品专区 | 国产精品无码久久四虎| 久久男人Av资源网站无码软件| 亚洲伊人久久综合中文成人网| 久久精品国产69国产精品亚洲| 久久久久久九九99精品| 亚洲精品乱码久久久久久蜜桃不卡 | 国产精品日韩欧美久久综合| 久久精品国产清高在天天线| 伊人色综合久久天天人手人婷 | 日韩亚洲欧美久久久www综合网| 午夜精品久久久久久毛片| 免费久久人人爽人人爽av| 亚洲精品tv久久久久| 久久中文字幕无码专区| 久久久精品久久久久久 | 亚洲AV无一区二区三区久久| 99久久香蕉国产线看观香| 久久人与动人物a级毛片| 亚洲AV日韩精品久久久久| 热re99久久精品国99热|