As the first step in the decommissioning of the site has been converted to read-only mode.

Here are some tips for How to share your SAS knowledge with your professional network.

Tips Talk:Making Macro Variables READONLY

From sasCommunity
Jump to: navigation, search

Good tip. I would suggest adding wording that says to click on the see also links to see the syntax. When I first read this, I tried to find this in the collisions article. --Don Henderson (talk) 18:09, 10 February 2015 (CST)

Added some syntax and a caveat. Creating an article is a good idea. --Art Carpenter (talk) 13:01, 11 February 2015 (CST)

Good tip. Scary option! You may want to include a note regarding how incorporating this option in existing code could easily end up destroying previously tested code. --Art T 18:39, 10 February 2015 (CST)

Agree. If misused it could cause quite a bit of havoc. --Art Carpenter (talk) 13:00, 11 February 2015 (CST)

Useful tip. Rather than just having links to resources on external websites, I think it would be helpful to also have some wiki articles that expand on this tip. To get the ball rolling, I added a wikilink to macro variables, and will (soon) add a link back here from there. I can imagine a few applications for read-only macro variables, so wonder if the tip might benefit from an example, or two, of some potential uses. - Cameron (talk) 05:35, 11 February 2015 (CST)

I have something that might be a good example - loading system parameters for an application from a parameter file. I need to see if I have already written it up as a wiki article. If so, I will add it there. If not, I will create an article and mention the use of READONLY. --Don Henderson (talk) 06:57, 11 February 2015 (CST)

Good tip. Looking forward to trying the code in 9.4 when we get it.

This is a good tip to know. I just tried the sample in 9.4 and got the following:
ERROR: The variable DSN was declared READONLY and cannot be modified or re-declared.
READONLY is also mentioned in New Macro Features Added in SAS® 9.3 and SAS® 9.4.
- paulkaefer (talk) 08:59, 22 June 2016 (CDT)