Hey SAS-C!
Just FYI.
Bart
20231009
Available as usual at: https://github.com/yabwon/SAS_PACKAGES
Changes:
%generatePackage()
macro.Thanks to Richann Watson for finding and reporting a but in the %generatePackage()
macro.
Trying to read this description and some of the code...
Why do you need to complicate things by having two separate macros for loading one package versus loading multiple packages? Why not just accept a normal space delimited list of packages?
%macro loadPackage
/* Load SAS Packages */
(packageNames
/* Space delimited list of Package names with optional version numbers */
/* Examples: */
/* %loadPackage(myPackage1) */
/* %loadPackage(myPackage1 yourPackage2) */
/* %loadPackage(myPackage1(1.7) yourPackage2(4.2)) */
The %loadPackage() was the first, with all its options.
It was a bit later when I realised that I could add some "syntactic sugar" to replace:
%loadPackage(myPackage1)
%loadPackage(myPackage2)
%loadPackage(myPackage3)
%loadPackage(myPackage4)
with
%loadPackageS(myPackage1, myPackage2, myPackage3, myPackage4)
The idea was: "different packages may have different loading options which can be customised" if you want to do customisation then load it in separate calls. If you just need a "simple" load of them all, you can use syntactic sugar of %loadPackageS().
But I see a development route in your suggestion! 🙂
Bart
Registration is now open for SAS Innovate 2025 , our biggest and most exciting global event of the year! Join us in Orlando, FL, May 6-9.
Sign up by Dec. 31 to get the 2024 rate of just $495.
Register now!
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.
Ready to level-up your skills? Choose your own adventure.