Proposal: new error return code for unprocessed options
Tim Tautges
tautges at mcs.anl.gov
Tue Nov 3 13:13:20 CST 2009
Hi all,
In the current interface, the load and save functions allow the application to pass in options in the form of a
string. However, there is no way for the implementation to let the application know that some of those options were not
interpreted. The only recourse is to not indicate an error, or to pass back a generic failure. Since options should be
optional, a generic failure is not sufficient. Therefore:
Proposal: Add a new error code "iBase_OPTION_NOT_PROCESSED"
Behavior:
If one of the options in the option string passed to any iMesh or iGeom functions are not interpreted by the
implementation, this error type is returned. The list of options not processed should appear in the error string, which
can be retrieved using the getDescription function.
Motivation:
Allows implementations to not interpret options passed by the application, and allows application to decide whether to
fail or not when this occurs.
- tim
--
================================================================
"You will keep in perfect peace him whose mind is
steadfast, because he trusts in you." Isaiah 26:3
Tim Tautges Argonne National Laboratory
(tautges at mcs.anl.gov) (telecommuting from UW-Madison)
phone: (608) 263-8485 1500 Engineering Dr.
fax: (608) 263-4499 Madison, WI 53706
More information about the tstt-interface
mailing list