Path: utzoo!attcan!uunet!know!cs.utexas.edu!yale!mintaka!spdcc!tauxersvilli!alphalpha!nazgul
From: nazgul@alphalpha.com (Kee Hinckley)
Newsgroups: comp.sys.apollo
Subject: Re:  Invoking a program called "next" from an Aegis shell
Message-ID: <1990Oct20.043702.3726@alphalpha.com>
Date: 20 Oct 90 04:37:02 GMT
References: <9010191547.AA20147@richter.mit.edu>
Organization: asi
Lines: 23

In article <9010191547.AA20147@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes:
>With the limitations you give, there is no solution. The Aegis shell will always find
>a reserved word ("next") before it finds a file in your search path.

I don't have the original message here, but I can guess.  It is strange
that "next" is caught as a reserved keyword.  Once upon a time all of
the keywords were reserved all of the time.  I fixed them (when I was at
Apollo, obviously) to that things like "then" and "else" were only
active when you were actually in an "if" construct.  I don't recall
why "next" didn't make it into that category.  Of course some people
might consider being valid sometimes and not others to be a bug too,
but what can you do?
						-kee


-- 
Alphalpha Software, Inc.	|	motif-request@alphalpha.com
nazgul@alphalpha.com		|-----------------------------------
617/646-7703 (voice/fax)	|	Proline BBS: 617/641-3722

I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.