--- Comment #6 from yuanfei8077 at gmail dot com 2006-10-02 14:19 ---
Subject: Re: Rule that binding rvalue to a refernce need a copy ctor don't
work
Thank you Andrew, appreciate your help on this topic.
-Kelvin
On 1 Oct 2006 20:33:33 -, pinskia at gcc dot gnu dot org
<[EMAIL PR
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-10-01 20:33 ---
(In reply to comment #3)
> Plesae seee Comment #2 From Kelvin 2006-09-28 23:25 [reply].
>
> In addition 2 questions I raised in the Commet2. I also have one more
> question
> about the rule "bind an rvalue to a re
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-09-29 04:14 ---
(In reply to comment #3)
This is not the correct place to ask for help with knowing what is wrong with
your code, you should ask the news list: comp.lang.c++ or something closely
related.
I might look at your code th
--- Comment #3 from yuanfei8077 at gmail dot com 2006-09-29 03:02 ---
Plesae seee Comment #2 From Kelvin 2006-09-28 23:25 [reply].
In addition 2 questions I raised in the Commet2. I also have one more question
about the rule "bind an rvalue to a reference,
we need to let copy ctor of t
--- Comment #2 from yuanfei8077 at gmail dot com 2006-09-28 23:25 ---
Subject: Re: Rule that binding rvalue to a refernce need a copy ctor don't
work
Hi Andrew,
You are right, I am omitting the code, however, my question is:
1)
> t.cc:38: error: 'MemAllocator::MemAllocator() [with Ty
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-09-28 13:39 ---
There is no
tdat_hash_map(_Alloc&) in the sources.
Adding one makes it get past that error and then we get:
t.cc: In constructor tdat_hash_map<_AllocType>::tdat_hash_map(const
_AllocType&) [with _AllocType = MemAllo
