Throwing exceptions vs validating
I am conflicted between validating and/or throwing an exception.
In the general case what would be the best practice? It is sort of hard for me to describe exactly what I envision, but in short - I can validate or check everything before doing an operation or I could just let the operation perform itself and handle any exceptions that arise.
For example (and I remind you - I am asking for best practices for the general case, not this specific example):
Let's say I am copying some files. I can first enumerate through all files that will be copied, verify all source and destination directories exist and that the full paths of any copied files will not be longer than 260 characters, etc. or I could have a try-catch
block that will handle every possible exception the copy method could throw.
Currently I am not sure which would be better. I have such a validating method but would also prefer to handle exceptions as well, just in case (because I have the spare time and resources).
Again, I'm asking for the best practices in the general case.
validation exception-handling
add a comment |
I am conflicted between validating and/or throwing an exception.
In the general case what would be the best practice? It is sort of hard for me to describe exactly what I envision, but in short - I can validate or check everything before doing an operation or I could just let the operation perform itself and handle any exceptions that arise.
For example (and I remind you - I am asking for best practices for the general case, not this specific example):
Let's say I am copying some files. I can first enumerate through all files that will be copied, verify all source and destination directories exist and that the full paths of any copied files will not be longer than 260 characters, etc. or I could have a try-catch
block that will handle every possible exception the copy method could throw.
Currently I am not sure which would be better. I have such a validating method but would also prefer to handle exceptions as well, just in case (because I have the spare time and resources).
Again, I'm asking for the best practices in the general case.
validation exception-handling
add a comment |
I am conflicted between validating and/or throwing an exception.
In the general case what would be the best practice? It is sort of hard for me to describe exactly what I envision, but in short - I can validate or check everything before doing an operation or I could just let the operation perform itself and handle any exceptions that arise.
For example (and I remind you - I am asking for best practices for the general case, not this specific example):
Let's say I am copying some files. I can first enumerate through all files that will be copied, verify all source and destination directories exist and that the full paths of any copied files will not be longer than 260 characters, etc. or I could have a try-catch
block that will handle every possible exception the copy method could throw.
Currently I am not sure which would be better. I have such a validating method but would also prefer to handle exceptions as well, just in case (because I have the spare time and resources).
Again, I'm asking for the best practices in the general case.
validation exception-handling
I am conflicted between validating and/or throwing an exception.
In the general case what would be the best practice? It is sort of hard for me to describe exactly what I envision, but in short - I can validate or check everything before doing an operation or I could just let the operation perform itself and handle any exceptions that arise.
For example (and I remind you - I am asking for best practices for the general case, not this specific example):
Let's say I am copying some files. I can first enumerate through all files that will be copied, verify all source and destination directories exist and that the full paths of any copied files will not be longer than 260 characters, etc. or I could have a try-catch
block that will handle every possible exception the copy method could throw.
Currently I am not sure which would be better. I have such a validating method but would also prefer to handle exceptions as well, just in case (because I have the spare time and resources).
Again, I'm asking for the best practices in the general case.
validation exception-handling
validation exception-handling
asked Nov 21 '18 at 10:49
J. DoeJ. Doe
159113
159113
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53410454%2fthrowing-exceptions-vs-validating%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53410454%2fthrowing-exceptions-vs-validating%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown