Date:         Fri, 10 Aug 2001 13:31:24 -0700
Reply-To:     Pete Lund <pete.lund@NWCSR.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Pete Lund <pete.lund@NWCSR.COM>
Subject:      Re: Suggestion: Language improvement
In-Reply-To:  <sb73c26e.007@SLCM02.firsthealth.com>
Content-Type: text/plain; charset="us-ascii"

I know Jack's intent is for some warning as to mismatched blocks, whatever
type they may be.  There is a baby step toward this end in V8 - at least one
that allows you to match do...end statements.  In the Enhanced Editor, if
you place the cursor anywhere inside a do...end block and hit alt-] (or
alt-[) the cursor will toggle from the "do" to the "end".  It's quite
helpful with multiple nested loops to track what goes with what.  Doesn't
quite do what Jack wants, but at least it's a step in the right direction.

----------------------------------------------------------------------------
---
Pete Lund
Northwest Crime and Social Research, Inc.
313-D Fifth Ave SE
Olympia, WA   98501
(360) 528-8970  - voice
(360) 280-4892  - cell
(360) 570-7533  - fax
pete.lund@nwcsr.com
www.nwcsr.com
----------------------------------------------------------------------------
---



-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU]On Behalf Of Jack
Hamilton
Sent: Friday, August 10, 2001 10:16 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Suggestion: Language improvement


It would be helpful to allow a marker of some kind on the END statement to
indicate what the END is closing.  For example:

   select (a);
      when (1)  /* do something */'
      /* More stuff */
   end select;

In the more general case, you might allow

   label: do i = 1 to 12;
      * Stuff;
      end label;


This would make it easier to follow nested loops, and would allow the
compiler to detect some coding errors.




--
JackHamilton@FirstHealth.com
Development Manager, Technical Group
METRICS Department, First Health
West Sacramento, California USA