Message78452
Whenever the documentation says "you must not" it really says "don't do
that or your application *will* crash, burn and die"... Of course I can
allocate storage for the string, copy it's content and then free or -
nothing will happen. How would it cause a crash - it's my own pointer.
That's exactly the line between "not required to", "should not" and
"must not": The current wording suggests that I may not even touch e.g.
malloc which is confusing and in fact to be ignored in it's current state. |
|
Date |
User |
Action |
Args |
2008-12-29 12:47:39 | ebfe | set | recipients:
+ ebfe, loewis, georg.brandl, ggenellina |
2008-12-29 12:47:39 | ebfe | set | messageid: <1230554859.14.0.140483399752.issue4746@psf.upfronthosting.co.za> |
2008-12-29 12:47:38 | ebfe | link | issue4746 messages |
2008-12-29 12:47:37 | ebfe | create | |
|