锘??xml version="1.0" encoding="utf-8" standalone="yes"?>久久久青草婷婷精品综合日韩,欧美视频免费在线,亚洲韩国青草视频http://m.shnenglu.com/cheney-chen/category/6878.html learning symbian C++zh-cnMon, 19 May 2008 13:12:46 GMTMon, 19 May 2008 13:12:46 GMT60Name Conventions for Applications on Symbian OShttp://m.shnenglu.com/cheney-chen/articles/Name_Conventions_for_Applications_on_Symbian_OS.htmlcheneycheneySun, 27 Apr 2008 06:57:00 GMThttp://m.shnenglu.com/cheney-chen/articles/Name_Conventions_for_Applications_on_Symbian_OS.htmlhttp://m.shnenglu.com/cheney-chen/comments/48259.htmlhttp://m.shnenglu.com/cheney-chen/articles/Name_Conventions_for_Applications_on_Symbian_OS.html#Feedback1http://m.shnenglu.com/cheney-chen/comments/commentRss/48259.htmlhttp://m.shnenglu.com/cheney-chen/services/trackbacks/48259.htmlOverview

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: 

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

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

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

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



  • cheney 2008-04-27 14:57 鍙戣〃璇勮
    ]]>
    99久久国产综合精品成人影院| 久久久久青草线蕉综合超碰| 国产激情久久久久影院| 欧洲国产伦久久久久久久| 狠狠色综合网站久久久久久久高清| 无码人妻精品一区二区三区久久久 | 国产免费久久久久久无码| 99精品久久久久久久婷婷| 7国产欧美日韩综合天堂中文久久久久 | 久久久一本精品99久久精品88| 久久99精品久久久久久久不卡| 久久国产精品偷99| 国产精品国色综合久久| 亚洲中文久久精品无码| 色天使久久综合网天天| 青青草原综合久久大伊人导航| 国产精品一久久香蕉国产线看| 久久妇女高潮几次MBA| 性欧美大战久久久久久久| 99久久国产亚洲高清观看2024| 国产成人精品免费久久久久| 久久永久免费人妻精品下载| 伊人久久无码中文字幕| 伊人久久大香线蕉精品不卡| 久久综合五月丁香久久激情| 国产精品xxxx国产喷水亚洲国产精品无码久久一区 | 久久久久久久久久久精品尤物| 久久国产三级无码一区二区| Xx性欧美肥妇精品久久久久久| 久久精品嫩草影院| 国产AV影片久久久久久| 精品久久香蕉国产线看观看亚洲| 久久久久亚洲AV无码专区体验| AV无码久久久久不卡蜜桃| 亚洲乱码精品久久久久..| 国内精品九九久久精品| 久久精品无码一区二区WWW| 麻豆精品久久久久久久99蜜桃| 无码八A片人妻少妇久久| 亚洲国产另类久久久精品| MM131亚洲国产美女久久|