Next: Options
Up: The UUDeview Decoding Library
Previous: The File List
Most of the library functions return a value indicating success or the
type of error occurred. The following values can be returned:
- UURET_OK
- The action completed successfully.
- UURET_IOERR
- An I/O error occurred. There may be many reasons from ``File not
found'' to ``Disk full''. This return code indicates that the
application should consult errno for more information.
- UURET_NOMEM
- A malloc() operation returned NULL, indicating that
memory resources are exhausted. Never seen this one in a VM system.
- UURET_ILLVAL
- You tried to call some operation with invalid parameters.
- UURET_NODATA
- An attempt was made to decode a file, but no encoded data was found
within its parts. Also returned if decoding a uuencoded or
xxencoded file with missing ``begin'' line.
- UURET_NOEND
- A decoding operation was attempted, but the decoded data didn't have a
proper ``end'' line. A similar condition can also be detected for
BinHex files (where the colon is used as end marker).
- UURET_UNSUP
- You tried to encode using an unsupported communications channel, for
example piping to a command on a system without pipes.
- UURET_EXISTS
- The target file already exists (upon decoding), and you didn't allow
to overwrite existing files.
- UURET_CONT
- This is a special return code, indicating that the current operation
must be continued. This return value is used only by two encoding
functions, so see the documentation there.
- UURET_CANCEL
- The current operation was canceled, meaning that the Busy Callback
returned a non-zero value usually because of user request. The library
does not produce this return value on its own, so if your Busy
Callback always returns zero, there's no need to handle this
``Error''.
Next: Options
Up: The UUDeview Decoding Library
Previous: The File List
2002-04-14