home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!cs.utexas.edu!swrinde!gatech!concert!sas!mozart.unx.sas.com!sasdxk
- From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
- Subject: GetLastError() return values???
- Originator: sasdxk@skyhawk.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <BxGy4w.FtB@unx.sas.com>
- Date: Mon, 9 Nov 1992 21:53:19 GMT
- Nntp-Posting-Host: skyhawk.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 31
-
-
- Although I've found Appendix B in the Overviews manual, how is one
- supposed to relate the many possibilites for rc's that GetLastError()
- returns after a particular WNT function returns FALSE?
-
- E.G. How am I supposed to know the actual values GetLastError() will
- return after CreateFile fails? I think many of the values are the
- same as OS/2 such as ERROR_PATH_NOT_FOUND, ERROR_FILE_NOT_FOUND or
- ERROR_PIPE_BUSY but I sure as heck can't test for all the values in
- Appendix B each function call. I don't even want to look thru the
- 100's of calls to even GUESS what they might be!
-
- And indeed, most of the return values I could care less about, an
- error is an error and I'll print out a message and the user can look
- it up and modify his or the program's behaviour somehow :-)
-
- But what if I want to deal with certain types of errors? How does
- one find out the possibilities for a given function?
-
- In OS/2 the rc's were listed with each function and when porting
- software it would be nice to know the likely rc candidates. Or even
- if not porting an OS/2 app.
-
- Thanks,
-
- --
- Dave Kolb Opinions are mine not SAS'
- SAS Institute, Inc. EMAIL: sasdxk@unx.sas.com
- SAS Campus Drive - J206 Phone: (919) 677-8000 x6827
- Cary, NC 27513-2414 USA FAX: (919) 677-8123
-
-