We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If a SAS macro is defined like so:
%macro outer(); /* any amount of arbitrary code */ %macro inner(); %put inner; %mend; %inner() %put outer; %mend; %outer()
This is widely considered as bad practice, because the inner definition is recompiled every time the outer macro is invoked.
We should create a lint warning if a subsequent %macro is discovered before a %mend in a SAS program.
%macro
%mend
For reference, a more 'correct' way to have defined the above would have been:
%macro inner(); %put inner; %mend; %macro outer(); /* any amount of arbitrary code */ %inner() %put outer; %mend; %outer()
Rule name: noNestedMacros
noNestedMacros
The text was updated successfully, but these errors were encountered:
🎉 This issue has been resolved in version 1.6.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
If a SAS macro is defined like so:
This is widely considered as bad practice, because the inner definition is recompiled every time the outer macro is invoked.
We should create a lint warning if a subsequent
%macro
is discovered before a%mend
in a SAS program.For reference, a more 'correct' way to have defined the above would have been:
Rule name:
noNestedMacros
The text was updated successfully, but these errors were encountered: