Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!mcnc!decvax!decwrl!hplabs!hpda!hpcuhb!hpcllla!hpclisp!hpclscu!shankar
From: shankar@hpclscu.HP.COM (Shankar Unni)
Newsgroups: comp.lang.pascal
Subject: Re: Scope question
Message-ID: <950009@hpclscu.HP.COM>
Date: 31 Mar 88 23:29:38 GMT
References: <718@virginia.acc.virginia.edu>
Organization: HP ITG/ISD Computer Language Lab
Lines: 32

/ hpclscu:comp.lang.pascal / (Steve Losen) / 11:40 am  Mar 29, 1988 /
> program test(output);
> 	const c = 10;
> 
> procedure junk;
> 	const c = c;  { Shouldn't this be an error ? }
> begin
> 	writeln(c)
> end;

This is simply a case of the general class of scoping violations that should
be detected by a conforming implementation (redefining an inherited item
after using it). Consider:

   program foo;
   type
      blah = <...>;

      procedure bar;
      type
	 blahptr = ^blah;  (* quick, which blah does this point to? *)
	 blah = <...>;

Shankar.

(Obviously, the berkeley pc does not conform to the standard. Of course, 
*nothing* that Berkeley does conforms to standards :-)

  whirrr... (shields up, captain)

)

--scu