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 (February 1998, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 3 Feb 1998 03:45:51 -0500
Reply-To:     Undetermined origin c/o LISTSERV administrator
              <owner-LISTSERV@UGA.CC.UGA.EDU>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
Comments:     RFC822 error: <E> "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o LISTSERV administrator
              <owner-LISTSERV@UGA.CC.UGA.EDU>

place in the syntax chart where the next token could be either a dataset name or a number. For instance, if the parser encounters a step boundary and the next few characters are:

DATA 12345678; SET 87654321; RUN;

Then a reasonable parser can conclude we are attempting to define a dataset named 12345678. There are good reasons to forbid variable names from beginning with digits (that is why 0C4X cannot be coded C4X), but those reasons do not apply to dataset names.

Tim ----------------------[Reply - Original Message]----------------------

Sent by:"Jack Hamilton" <jack_hamilton@HCCOMPARE.COM> Tim Berryhill 3rd time <TWB2%Rates%FAR@BANGATE.PGE.COM> wrote:

>Although there should never be confusion whether something is a number or the >beginning of a dataset name, I expect a dataset name cannot begin with a digit.

The hexadecimal constant 0C4X is a number, but could be confused with a name if names could start with digits (which they can't, only letters and the underscore).

=====================================================================


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