View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0000151 | mercury | Bug | public | 2010-05-30 16:25 | 2010-07-07 17:53 | ||||||||
Reporter | pbone | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | trivial | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0000151: Incorrect documentation for string.unsafe_set_char | ||||||||||||
Description | James Cussens found that the documentation for this standard library predicate and function doesn't match the implementation. The documentation says that it is a constant time operation but it involves a strcpy. The unsafe part of the name says that there is no bounds check and that a strlen call isn't performed. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files |
|
![]() |
|
juliensf (administrator) 2010-05-30 16:28 |
The documentation refers to the commented out mode of unsafe_set_char, which is constant time. The problem is that the mode that is enabled isn't. |