When the code that reads Symbian, the possibility that feels the most incommensurate often sees PushL and Pop function namely, still have even if what very much function has L or LC is suffixal. Actually this is the exceptional processing mechanism of Symbian. Defined a finger e.g. us, allocated a space to it, the program is sudden when but be in,using it appeared deadly and wrong break down, we affirm the address space that this finger takes up is to closed not to come back, in the process designing on PC this are likely the question is not big, memory is so much, and how long of have more than is needed was started again, but the architect of Symbian may think this is to be no good on the mobile phone, did a lot of designs to this so. Symbian has a Clean Up Stack, when use finger, press finger into inn with PushL, make an inn is being played with Pop after giving out, when the function that if the inter calls a likelihood to bring about,breaks down if really appeared problem, so Clean Up Stack can pass the analyse form function that transfers this finger to reclaim the space that take up. These likelihoods bring about the function that break down to be called in Symbian likelihood the function of Leave, added a L in the rear of these function so. And add the function with suffixal LC to make clear this function already interiorly presses finger into Clean Up Stack with PushL, when calling need not reoccupy PushL, direct attune is gone with Pop already but. Clean Up Stack still provided function of a PopAndDestroy, after playing an inn namely again finger of destroy by melting or burning. Carry incidentally, formal because had mechanism of Clean Up Stack, the order that so Symbian follows VC it seems that in some places is not quite same, the tectonic function e.g. a lot of kinds need not, construct with NewL or NewLC, the operator New() when allocating an address also became New(ELeave) . Afore-mentioned content can see the memory in foundation of Symbian process designing manage.
Him Symbian defined the data kind of one caboodle, if do not think picky word, darling still those who use these types is good. Say simply, whole model have TInt and TUint, divide those who be 8 again among them, 16 with 32, be like TInt8, TInt16, TInt32; Text type is TText, fractionize is TText8 and TText16, but interior is Unicode, actually so interior cites should be TText16; Bool it is TBool, corresponding value has ETrue and EFalse; Floating-point it is TReal, but divide again for TReal32 and TReal64; Still one cites type TRefByvalue<T> , be with pattern plate kind the form offers.
Because Symbian is of strong more object-oriented design, in our common string so this change is compared big, descriptor cries in Symbian. The most rock-bottom is two abstraction kind TDesC and TDes, actually TDes also is successive TDesC, the C letter in TDesC is the meaning of constant Constant. What bring C letter end namely is the constant of the definition, can not revise, and the has a the biggest length restriction that does not carry C, can revise, same argument also is below. Descriptor of pressing with a finger is TPtrC and TPtr, be similar to the Char * in C ; Buffer descriptor (Buffer Descriptor) is TBufC and TBuf, be similar to Char [] ; Piling a descriptor is HBufC, be similar to (the usage of Char *)malloc(length 1) . Specific when using, afore-mentioned type divides those who be 8 to mix 16 again. Cite a case:
Previous 1 2 34 Next