Message313450
> GetLastError() docs officially scare us
I believe this is a case where the docs were updated from intended/correct behavior to actual behavior, which happens from time to time and is never clearly marked.
As I say, they are _supposed_ to leave the error unchanged unless they return a value that indicates an error occurred, but some APIs behave incorrectly. The docs are simply documenting that fact. (It turns out reality is more useful than fantasy ;) though I do wish they were clearer about that) |
|
Date |
User |
Action |
Args |
2018-03-08 17:29:23 | steve.dower | set | recipients:
+ steve.dower, paul.moore, tim.golden, zach.ware, izbyshev |
2018-03-08 17:29:23 | steve.dower | set | messageid: <1520530163.14.0.467229070634.issue33030@psf.upfronthosting.co.za> |
2018-03-08 17:29:23 | steve.dower | link | issue33030 messages |
2018-03-08 17:29:23 | steve.dower | create | |
|