|
pico]OS
1.0.4
|
Macros | |
| #define | NOSCFG_FEATURE_REGISTRY 1 |
| #define | NOSCFG_FEATURE_REGQUERY 1 |
| #define | NOSCFG_FEATURE_USERREG 1 |
| #define | NOS_MAX_REGKEYLEN 8 |
| #define | NOS_REGKEY_PREALLOC 4 |
| #define NOS_MAX_REGKEYLEN 8 |
Maximum length a registry key can have. This define sets the maximum length (characters) a registry key can have. If the registry is enabled, this define must be set to at least 4.
| #define NOS_REGKEY_PREALLOC 4 |
Registry key housekeeping. When ever a new key is created, the nano layer needs to call malloc(). If this define is set to a number greater than 1, one malloc-call is used to allocate memory for a bunch of keys (the count of keys is defined here). This reduces overhead in the memory manager, but increases the code-memory usage a bit.
| #define NOSCFG_FEATURE_REGISTRY 1 |
Enable registry support. If this definition is set to 1, the registry functions are added to the user API.
| #define NOSCFG_FEATURE_REGQUERY 1 |
Enable the query for registry keys. If this definition is set to 1, the functions nosRegQueryBegin, nosRegQueryElem and nosRegQueryEnd will be added to the user API.
| #define NOSCFG_FEATURE_USERREG 1 |
Enable the user registry. The user has access to its own branch in the registry. He can store there pairs of strings and binary values. (A text string is also called a "registry key" that is assigned to a binary value, such as a memory pointer or integer number). An application can now ask the system for a registry key and will get the belonging binary value, or vice versa. If this definition is set to 1, the functions nosRegGet, nosRegSet and nosRegDel will be added to the user API.
1.8.1