A descriptor is a data structure that describes a string or an array. Each descriptor contains information that describes the type of the data being referenced, the size of the data, and the address of the data. It also includes a description of the storage used for the data, typically static or dynamic. Descriptors are passed by reference.

You will have to search the filesystem for files of the same size as the file you're reading, and compare information in them to find the file you're working on. See similar questions...

CPCAB Descriptors are attached to the main qualification titles, and can either refer to the model, e.g. humanistic, psychodynamic etc, or to the context or setting of the work, e.g. Certificate in Counselling Skills - Working with Addictions; Certificate in Counselling Skills - Working With Young People. Depending on what options colleges make available, trainees can choose between a Humanistic, Psychodynamic or Integrative Diploma. See similar questions...

A distance descriptor is a structural feature consisting of two atoms or groups that have a fixed spatial distance from each other. The number and type of atoms and bonds that separate the two end groups of a distance descriptor are indeterminate. See similar questions...

A global descriptor is a property of a chemical such as LogP, graph index, or molecular weight. A nonglobal descriptor is a substructure or fragment imbedded in a molecule. See similar questions...

A#11.9: Use the fileno() macro. This is defined in <stdio.h> as of GNO v2.0.6. For earlier versions you will have to add it in yourself. The proper macro definition for the ORCA/C headers is: #define fileno(p) ((p)->_file) Q#11.10: My (ported) source requires <sys/file.h>. Why isn't it there? A#11.10: <sys/file.h> has been superceded by <sys/fcntl.h>. Update your sources. Q#11.11: Why, when I '#include <types. See similar questions...

A distance descriptor can have the same role as a biophore, as a predictor biological activity. However, a distance descriptor is structurally different from biophores and other fragments, which are connected linear chains of atoms or groups. See similar questions...

Apache Labs is designed to host a very large number of small labs, some of which will be promoted, but must of which would lie idle or die. Machine-readable descriptors allow us to automate browsing and managing the various labs and knowing who is responsible or who to contact. Making it a mandatory requirement helps in making sure that every lab complies and distributes the cost of maintaining the project. See similar questions...

If you are exiting, I have been assured by Andrew that all unixes will close open file descriptors on exit. If you are not exiting though, you can just close it with a regular close() call. See similar questions...

This flowchart may help. It's taken from my book, Symbian OS Explained (page 76), with some modification: See similar questions...

This function can still be called with a modifiable descriptor like a TPtr as the argument, because these derive from TDesC (a TPtr is a specialised type of TDes). Inside the function, only the TDesC operations may be performed on the parameter. Its contents will not be changed, even if you have passed in a modifiable, TDes-derived descriptor. See similar questions...

Descriptors can be stored on the stack or heap. The normal limitations apply as for other Symbian OS variables: Stack descriptors should be kept small: a 256 byte limit (128 double-byte characters) is a good guide. See 6. Large stack-based descriptors for more information about how to avoid accidentally wasting stack space through use of Symbian OS descriptor typedefs and stack-based classes which encapsulate large descriptors. See similar questions...

You cannot call this function with a non-modifiable descriptor, which makes sense because you don't want a read only descriptor to be modified. Inside the function you can both read from and write to the parameter. Remember that the descriptor must already have sufficient space in it for the data to expand into, if necessary. If there isn't, you'll get a panic. See similar questions...

Yes you can, but don't. For example you could specify your function requiring a parameter passed a TBuf<10>&. But what if the caller has got a TPtrC, or an HBufC, or even a TBuf<11>? This means that they won't be able to call your function without some extra hassle to fit in with exactly what you have specified. TDes and TDesC are the most general types you can use for your function parameters. Oh how much pain has this one caused? Missing out that little & symbol makes all the difference. See similar questions...

These days, it's not necessary to use the Symbian cast macros (eg REINTERPRET_CAST) since these are simply defined as the equivalent C++ standard (eg reinterpret_cast). They're a legacy from when GCC didn't support the casts. See similar questions...

Why is the original _L macro now deprecated in all but test code? These have the advantage of being used in place rather than declared separately, for example: Well, the text, for example "TEST SERVER" is built into ROM as a basic, NULL-terminated C style string, with no initial length member. Because the layout of the stored literal is not like that of a descriptor, it means that when each instance of the literal is used, a temporary TPtrC must be constructed around the data in ROM. See similar questions...

If it needs to be modifiable, use a TBuf. If it's constant, use a TBufC. You'll need to specify the size of stack space allocated for the descriptor's data. In reality, you probably wouldn't do this for a non-modifiable descriptor, since you can use the literal, KFred directly by calling the operator()() (as I'll describe separately in 22. What are literal descriptors?). That is, instead of creating constantFred, you could just call KFred(). See similar questions...