The semicolon after the macro call will never be used, will it? (actually if it is part of the logic of the macro-generated code, it should be inside the macro itself).
The only reasonable case when a semicolon will be used after the macro call is when it closes a non-macro statement, as in
title %write_title(big, red, bold);
but then the semicolon is there to close the title statement, not as part of the macro call.
>I have known programmers who put a semicolon in empty lines as spacers.
Unless you are one of these and like extra and unused semicolons, a semicolon after a macro call makes no sense.
My 2 cents, to each their own and all that. Having an extra ; is not a big sin (though it sometimes hides bad understanding of how macros work).
Edited. The deficient color parser is sadly a reason to use an ending semicolon, as it gets confused without this explicit statement delimiter.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.