-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errorabend - Why force SAS to close when it comes across an error? #1
Comments
Hi Jared,You are exactly right: I use that option to make sure the code stops with an error. I always use that option in all my code, other than in cases when I know that it will generate an error that I’m okay with. I think it would be risky to run code without it, in case you don’t notice an important mistake. -EdPlease pardon my brevity - sent from my mobile. On Jun 30, 2023, at 8:42 PM, Jared Flake ***@***.***> wrote:
Hi Ed,
Thanks for making this available - very useful!
Can you help me understand why you use the ERRORABEND option in your macro? Is it caution to ensure you don't move forward with an error from the macro output, or is there more to it than that?
Do you also use it outside of your macros? I'm wondering if I should add the NOERRORABEND option at the end of the macro or adopt using ERRORABEND more broadly in my code.
Thanks!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Thanks for the quick response and explanation! Thanks again for providing
the code.
On Sun, Jul 2, 2023 at 4:14 AM ed-dehaan ***@***.***> wrote:
Hi Jared,You are exactly right: I use that option to make sure the code
stops with an error. I always use that option in all my code, other than
in cases when I know that it will generate an error that I’m okay with. I
think it would be risky to run code without it, in case you don’t notice an
important mistake. -EdPlease pardon my brevity - sent from my mobile. On
Jun 30, 2023, at 8:42 PM, Jared Flake ***@***.***> wrote:
Hi Ed,
Thanks for making this available - very useful!
Can you help me understand why you use the ERRORABEND option in your
macro? Is it caution to ensure you don't move forward with an error from
the macro output, or is there more to it than that?
Do you also use it outside of your macros? I'm wondering if I should add
the NOERRORABEND option at the end of the macro or adopt using ERRORABEND
more broadly in my code.
Thanks!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you are subscribed to this thread.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKGXHZWJIO5OXT55LMTNTSDXOFCYVANCNFSM6AAAAAAZ2EEIC4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Jared Flake
Ph.D. Candidate in Accounting
Boston College
Carroll School of Management
Fulton Hall 548
***@***.*** | 480-340-0545
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Ed,
Thanks for making this available - very useful!
Can you help me understand why you use the ERRORABEND option in your macro? Is it caution to ensure you don't move forward with an error from the macro output, or is there more to it than that?
Do you also use it outside of your macros? I'm wondering if I should add the NOERRORABEND option at the end of the macro or adopt using ERRORABEND more broadly in my code.
Thanks!
The text was updated successfully, but these errors were encountered: