home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!engr.uark.edu!mbox.ualr.edu!eivax.ualr.edu!hood
- Newsgroups: comp.lang.c++
- Subject: Re: Why X::X(X &a), not X::X(X a) ?
- Message-ID: <1993Jan20.130006.1@ualr.edu>
- From: hood@ualr.edu
- Date: 20 Jan 93 13:00:06 CST
- Reply-To: hood%eivax@ualr.edu
- References: <1993Jan12.155159.22650@mobil.com> <harvey.726884989@regina> <1993Jan15.092416.1@ualr.edu> <884@ulogic.UUCP>
- Organization: University of Arkansas at Little Rock
- Nntp-Posting-Host: eivax.ualr.edu
- Lines: 24
-
- In article <884@ulogic.UUCP>, hartman@ulogic.UUCP (Richard M. Hartman) writes:
- > In article <1993Jan15.092416.1@ualr.edu> hood%eivax@ualr.edu writes:
- >> Since the copy constructor should not normally
- >>modify the source object a better declaration would be X::X( const X a)
- >
- > I am assuming a typo. Shouldn't that be:
- >
- > X::X(const X &a) ?
- >
-
- Your right, it was a typo; the way you show it is correct.
-
- William G. Hood
- University of Arkansas at Little Rock
- Internet: hood%eivax@ualr.edu
-
- >
- >
- > -Richard Hartman
- > hartman@ulogic.COM
- >
- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- > "Who knows what evil lurks in the hearts of men?"
- >
-