D
dbeavon
Guest
Is anyone aware of object-oriented wrapper methods for the portable OS commands (OS-DELETE and similar)? The usage patterns for those OS-whatever commands is not what someone would expect when writing modern code (OO and SEH). Take a look at the following from the docs for example: Although an error can occur during execution of this statement, the statement does not generate an error message, raise an error condition, or affect the program's flow in any way Okay..... who wants to use an API that will quietly fail to do what you ask of it? This type of API doesn't seem reliable or trustworthy. I understand that these method calls must be paired up with a following call to the OS-ERROR function, but why make that manual (and optional)? The worse thing about those subsequent methods to check for errors (eg "OS-ERROR") is that it clutters the code, but if you choose not to do them straight-away then the runtime may overwrite the related details. An OO-friendly wrapper for this stuff would be greatly appreciated.
Continue reading...
Continue reading...