LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (June 1997, week 5)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Mon, 30 Jun 1997 10:12:24 PDT
Reply-To:   TWB2%Rates%FAR@BANGATE.PGE.COM
Sender:   "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:   Tim Berryhill 3rd time <TWB2%Rates%FAR@BANGATE.PGE.COM>
Subject:   Re: /* Considered Harmful

John, Just for the record, in the One True OS, the combination /* in columns 1 and 2 terminate an in-line dataset (unless you code the JCL DLM option). The most common in-line dataset is SYSIN, which is the source. I think this catches us dinosaurs once or twice a decade when we start a /* comment in column 1 and MVS ignores the rest of the program.

Tim Berryhill - Contract Programmer and General Wizard TWB2@PGE.COM or http://www.aartwolf.com/twb.html Frequently at Pacific Gas & Electric Co., San Francisco The correlation coefficient between their views and my postings is slightly less than 0 ----------------------[Reply - Original Message]----------------------

Sent by:John Herbert <herbertj@BRE.CO.UK>

> /* Operating System Pre-emption: >The '/*' character combination is a reserved reference in certain >environments (specifically, /* Jurassic Iron, but there's a lot of it >still around). I understand that it is possible to specify alternate >handling of this character combination under mainframe environments, but >this introduces yet another barrier to code portability. --Are you saying that in some environments, if you *type* "/*" you'll have problems? If it's in the code, there should be no problem.


Back to: Top of message | Previous page | Main SAS-L page