C++ Primer, Fourth Edition

[huangshan]

hi all

I read "C++ Primer, Fourth Edition" ,
but can't understand this sentence
"By making the parameters const references, we allow types that do not allow
copying."
in "16.1. Template Definitions" .

who can tell me?
thanks

[Daniel T.]

In article <eg**********@news.cn99.com>,
"huangshan" <hu**************@hotmail.comwrote:

hi all

I read "C++ Primer, Fourth Edition" ,
but can't understand this sentence
"By making the parameters const references, we allow types that do not allow
copying."
in "16.1. Template Definitions" .

who can tell me?

class NonCopyable {
NonCopyable( const NonCopyable& );
NonCopyable& operator=( const NonCopyable& );
public:
NonCopyable();
};

void fn1( NonCopyable nc ); // this will fail to compile
void fn2( const NonCopyable& nc ); // this will compile

--
There are two things that simply cannot be doubted, logic and perception.
Doubt those, and you no longer$B%O(Bhave anyone to discuss your doubts with,
nor any ability to discuss them.

[Victor Bazarov]

huangshan wrote:

hi all

I read "C++ Primer, Fourth Edition" ,
but can't understand this sentence
"By making the parameters const references, we allow types that do
not allow copying."
in "16.1. Template Definitions" .

who can tell me?

class NoCopies {
NoCopies(NoCopies const&); // copying prohibited
public:
NoCopies(int);
};

void foo(NoCopies);
void bar(const NoCopies&);

int main()
{
NoCopies nc(42);
foo(nc); // error -- must be able to copy
bar(nc); // no error
}

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[Alf P. Steinbach]

* Victor Bazarov:

huangshan wrote:

>hi all

I read "C++ Primer, Fourth Edition" ,
but can't understand this sentence
"By making the parameters const references, we allow types that do
not allow copying."
in "16.1. Template Definitions" .

who can tell me?

class NoCopies {
NoCopies(NoCopies const&); // copying prohibited
public:
NoCopies(int);
};

void foo(NoCopies);
void bar(const NoCopies&);

int main()
{
NoCopies nc(42);
foo(nc); // error -- must be able to copy
bar(nc); // no error
}

Just to fill out the picture, the /current/ standard doesn't allow

bar( NoCopies( 42 ) );

because in the current standard, when binding a temporary to a reference
to const, the compiler is allowed to copy the temporary any number of
times, i.e. a copy constructor must be available.

So the phrasing "allow types that do not allow copying" allows an
interpretation where one believes more is allowed than is actually
allowed, but, types that do not allow copying are allowed as far as the
current standard allows (heh).

As I understand it this will be fixed in C++0x.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?