An Idea Exchange for SAS software and services

Comments
by Respected Advisor
on ‎01-21-2013 10:08 AM
Thank you! Good luck finding your shoes. - Pierre
by Super Contributor
on ‎01-21-2013 03:37 PM
Good afternoon Pierre! No luck for the shoes. There were colored running shoes but no colored walking shoes. I have to go to a sports store later. Here is cold but no snow. How about Montreal? How are you doing? 
by Respected Advisor
on ‎01-21-2013 04:19 PM
It's -16C here now but no wind or snow. I'm curious. Why walking shoes now? Why colored?
I just got a new assignment from my boss. He thought he had sent me his questions earlier, but forgot to add my address in his message. He has been waiting for my answer for a couple of weeks now. I'll be under pressure to come up with answers quickly now, I guess.
Is your holiday today because of the President inauguration? We don't get anything like that, but then, we don't have a President, we have a Queen, and we don't change Queens every 4 years!
by Super Contributor
on ‎01-21-2013 04:44 PM
It is the Martin Luther King(Civil right leader) holiday. There is a president day next month.  Boots are uncomfortable to walk for long time, running shoes are too cold for now, so I need walking shoes. I only have white or grey walking shoes, I am going to buy either green or red ones. 
For the new assignment,do you need to process the data or the data is ready for you to use? Hope you don't have to work more than 8 hours a day.
by PROC Star
on ‎04-14-2014 11:40 AM

So would your super comment nest?

If not, it doesn't seem much better to me than /* */ comments.  And since ] and > are used elsewhere, might be problematic?

I typically just use /* */ comments for my macro headers, and for examples inside I use * comments.

BTW, I wrote a paper a few years back on using SAS to generate automatic documentation of an autocall library:

http://www.nesug.org/proceedings/nesug04/po/po04.pdf

by Frequent Contributor
on ‎04-15-2014 04:08 PM

huh? nesting comments? I don't know of any language which can nest comments and i also see no reason for that.

And since ] and > are used elsewhere, might be problematic?

This was just an example. But i cannot imagine any valid SAS code containning ]]> unless arrays can be nested some day.

I typically just use /* */ comments for my macro headers, and for examples inside I use * comments.

I did not say that there are no workarounds. But using * comments might also be problematic (see http://www.nesug.org/proceedings/nesug05/pos/pos10.pdf for example). So usually i avoid them. This leads to a lot of /* */ comments in my macros. If i just want to comment out a large part of my code i get into trouble because there will be some */ tokens inside the code block i want to comment out.

by PROC Star
on ‎04-15-2014 05:17 PM

So if it can't nest, what makes it a super comment?  Seems like you have just asked for a second type of block comment, with the same functionality as /**/ block comments.   Benefit is you could use a [Comment] block to comment out a block of

code that includes /**/ blocks, and perhaps converse.  Is that right?

You are right, * comments can be problematic in macro definitions, but %* comments are safe.

by Occasional Contributor railfan1975
on ‎05-15-2014 10:25 AM

Actually, the nesting idea is cool.  There are lots of times I want to comment out a big block of code when debugging and have to go through and do it piece meal because of the comments documenting each part of it.  Begin able to wrap that in some kind of super comment block and not have to worry about /**/ or */ or /* or %* comments would be nice.

by Super User
on ‎05-15-2014 10:41 AM

How would that be different than highlighting the code and hitting CTRL+/?

by Occasional Contributor railfan1975
on ‎05-15-2014 10:50 AM

Here's my code:

Code

Code

/*Comment*/

Code

Code /*Comment*/

Code

If I highlight all but the first line and hit CTRL+/ I get:

Code

/*Code

/*Comment*/

Code

Code/*Comment*/

Code*/

Because of the nested /* */, it errors out.  It would be nice to to be able to do something like Andreas mentioned where I could have:

Code

<

>

and not get errors from the nested comments.

Idea Statuses
Top Liked Authors