https://bugs.documentfoundation.org/show_bug.cgi?id=148466
--- Comment #2 from Mike Kaganski <[email protected]> --- For comparison: I read many API docs in MSDN. There it is common for functions to *not* specify any specific error codes that the function *may* return in case of error (e.g., it is common to see "On error, the return value is 0. To get extended error information, call GetLastError", without any mapping of input values to error codes - e.g. [1]); or it may choose to document *some* possible error codes for important cases (that actually are needed for reasonable use of the API), and *also allow other codes* (e.g., [2]). IMO, the error codes are *to the greatest possible extent* are implementation detail, which should evolve together with improvements of the IDE. Trying to fix these would make them part of published API, which is binding, and *must be avoided as much as possible*. [1] https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-movefileexw [2] https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-movefiletransacteda -- You are receiving this mail because: You are the assignee for the bug.
