comparison: docs/Writerside/topics/properties.h.md
docs/Writerside/topics/properties.h.md
- changeset 1268
- a84403b0a503
- parent 1233
- 29e1c48d1a6c
equal
deleted
inserted
replaced
| 1267:d17eba9fae33 | 1268:a84403b0a503 |
|---|---|
| 94 If that is not possible for some reason, `cxPropertiesNext()` fails and returns `CX_PROPERTIES_BUFFER_ALLOC_FAILED`. | 94 If that is not possible for some reason, `cxPropertiesNext()` fails and returns `CX_PROPERTIES_BUFFER_ALLOC_FAILED`. |
| 95 | 95 |
| 96 If you want to reuse a `CxProperties` structure with the same config, you can call `cxPropertiesReset()`, even if the last operation was a failure. | 96 If you want to reuse a `CxProperties` structure with the same config, you can call `cxPropertiesReset()`, even if the last operation was a failure. |
| 97 Otherwise, you should always call `cxPropertiesDestroy()` when you are done with the parser. | 97 Otherwise, you should always call `cxPropertiesDestroy()` when you are done with the parser. |
| 98 | 98 |
| 99 > It is strongly recommended to always call `cxPropertiesDestroy` when you are done with the parser, | 99 > It is strongly recommended to always call `cxPropertiesDestroy()` when you are done with the parser, |
| 100 > even if you did not expect any allocations because you used `cxPropertiesUseStack()`. | 100 > even if you did not expect any allocations because you used `cxPropertiesUseStack()`. |
| 101 | 101 |
| 102 ### List of Status Codes | 102 ### List of Status Codes |
| 103 | 103 |
| 104 Below is a full list of status codes for `cxPropertiesNext()`. | 104 Below is a full list of status codes for `cxPropertiesNext()`. |
