Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!att!dptg!ulysses!andante!alice!ark
From: ark@alice.UUCP (Andrew Koenig)
Newsgroups: comp.lang.c++
Subject: Re: Modifying References
Message-ID: <10197@alice.UUCP>
Date: 30 Nov 89 18:01:17 GMT
References: <4280@cadillac.CAD.MCC.COM> <936@acf5.NYU.EDU> <1989Nov30.053552.6149@sjsumcs.sjsu.edu>
Distribution: na
Organization: AT&T Bell Laboratories, Liberty Corner NJ
Lines: 13

In article <1989Nov30.053552.6149@sjsumcs.sjsu.edu>, horstman@sjsumcs.sjsu.edu (Cay Horstmann) writes:

> Well, I suppose it would be logical to allow

> 	&r = b; // now r a reference to b?

> but it would be quite unintuitive.

It also wouldn't work.  What if r is an object of a class with
operator&() defined?
-- 
				--Andrew Koenig
				  ark@europa.att.com