You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, let's have a look at Writer.visitFromStream(COSStream obj) - if an IOException occurs, veraPDF will throw a RuntimeException. Why? Is it really the desired behavior that veraPDF (probably) terminates an application if (for example) the disk is full?
IMHO a library should never tear down an application - if the application should exit/terminate or not is the responsibility of the application. I usually would not expect that....
Bye,
Michael
The text was updated successfully, but these errors were encountered:
Hi again @michaelknigge I'll be leaving this open for now. The behaviour you describe sounds neither desirable or intentional and we'll review over the development period for the next release. Thanks.
I looked through the issues at https://app.codacy.com/app/veraPDF/veraPDF-parser/issues and asked myself if it is really the desired behavior that veraPDF throws RuntimeExceptions?
For example, let's have a look at Writer.visitFromStream(COSStream obj) - if an IOException occurs, veraPDF will throw a RuntimeException. Why? Is it really the desired behavior that veraPDF (probably) terminates an application if (for example) the disk is full?
IMHO a library should never tear down an application - if the application should exit/terminate or not is the responsibility of the application. I usually would not expect that....
Bye,
Michael
The text was updated successfully, but these errors were encountered: