| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000891 | FL5 | 4. Element, Byte, Record or other API | public | 2017-10-13 14:19 | 2018-03-05 07:55 |
|
| Reporter | Falk Reichbott | |
| Assigned To | Falk Reichbott | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | |
| Platform | General | OS | General | OS Version | General |
| Product Version | 5.1.15 | |
| Target Version | 5.2 | Fixed in Version | | |
|
| Summary | 0000891: Make record and byte interface thread save |
| Description | For the byte interface new entries will be implmented which are thread save but do not conform to the standard I/O interface.
For the record interface the current return code will be interpreted as a pointer to a structure of two shorts (16 bit values), with the first 16 bit containing the space for the error trace and the second short containing the return code. If the first short (high order half word) is not 0 then after the first 4 byte a remaining byte array can be used to store the error trace. This removes the global variable currently used to get the error trace later with a second call, which is not a thread save solution. |
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 