[prev] [thread] [next] [lurker] [Date index for 2006/08/26]
> I once looked at some Windows CE guts-related sources. You have > this huge networking module, reporting errors as integeres (what > else?). Then it's wrapped by a thin layer of shite, which checks > for errors and returns a SINGLE integer (what else?) indicating > that networking code failed, and throws the more specific integer > away. So there's this useless tree of error numbers, eventually > culminating in a boolean "tough luck!" message to the user. Windows is worse. There you have multiple layers which not only throw away the underlying errors, they *make error codes up* based on what the programmer thought was most likely, or to try and make some application that did something wrong if it got the "wrong" error code "not break" on a new version of Windows, or because of sheer stupidity... So you end up with network errors being reported as premissions errors, full disks being reported as permission errors, and permission errors being reported as full disks! Worse, because of the increasing use of shared libraries as "the API" instead of system calls, I'm starting to see the same things happen in what are otherwise basically UNIX systems, like Linux and OS X.There's stuff above here
Generated at 03:01 on 31 Aug 2006 by mariachi 0.52