Path: utzoo!attcan!uunet!decwrl!wuarchive!cs.utexas.edu!milano!cadillac!dsouza From: dsouza@optima.cad.mcc.com (Desmond Dsouza) Newsgroups: comp.lang.c++ Subject: Re: Assignments to reference variables [ and operator.() ] Message-ID: Date: 1 Oct 90 22:28:27 GMT References: <8445@jarthur.Claremont.EDU> <57570@microsoft.UUCP> <1677@lupine.NCD.COM> <57684@microsoft.UUCP> Sender: news@cadillac.CAD.MCC.COM Organization: MCC CAD Program, Austin, Texas Lines: 30 In-reply-to: jimad@microsoft.UUCP's message of 24 Sep 90 19:15:20 GMT In article <57684@microsoft.UUCP> jimad@microsoft.UUCP (Jim ADCOCK) writes: >... >"features" of the language as self consistent as possible. Lacking overloaded >op. forces a gratuitous lack of symmetry between usages of pointers and >references. >... >such a proposal. I am suggesting that allowing unary op. like unary op-> >would fix a lot of the current syntax problems for users exposed to confusing >mixtures of pointers and references with no apparent rhyme nor reason. I agree completely with Jim on this. The "confusing mixtures of pointers and references" can be somewhat remedied with an overloaded "." Assignable references are just one feature which could be implemented with this. -- Desmond. -- ------------------------------------------------------------------------------- Desmond D'Souza, MCC CAD Program | ARPA: dsouza@mcc.com | Phone: [512] 338-3324 Box 200195, Austin, TX 78720 | UUCP: {uunet,harvard,gatech,pyramid}!cs.utexas.edu!milano!cadillac!dsouza