Re: Compiler chooses conv ctor - why?
- From: "Cezary H. Noweta" <chncc@xxxxxxxxxxxxxxx>
- Date: Tue, 15 Apr 2008 04:09:55 +0200
Hello,
Victor Bazarov wrote:
Huh? Elimination of the copy is allowed, but not required. Even if it is forgone (the compiler decides to optimize it away), the copy-ctor has to be available _as_if_ it were used (12.8/15).
I know that checking of access or not would be stupid. It would involve
that the same program is ill-formed when not optimized and well-formed
when optimized. Assuming that access checking is an element of the copy
construction, and after 12.8[15] states that ,,an implementation is
allowed to omit the copy construction'' the situation has been not so
clear for me. Hopefully, newer working drafts have paragraph 12.8[16],
which unambiguously clears everything.
-- best regards
Cezary Noweta
.
- References:
- Compiler chooses conv ctor - why?
- From: Cezary H. Noweta
- Re: Compiler chooses conv ctor - why?
- From: Alex Blekhman
- Re: Compiler chooses conv ctor - why?
- From: Charles Wang[MSFT]
- Re: Compiler chooses conv ctor - why?
- From: Cezary H. Noweta
- Re: Compiler chooses conv ctor - why?
- From: Alex Blekhman
- Re: Compiler chooses conv ctor - why?
- From: Cezary H. Noweta
- Re: Compiler chooses conv ctor - why?
- From: Victor Bazarov
- Compiler chooses conv ctor - why?
- Prev by Date: Re: Array of char pointers.
- Next by Date: Re: COM Interface definition
- Previous by thread: Re: Compiler chooses conv ctor - why?
- Next by thread: Re: Compiler chooses conv ctor - why?
- Index(es):
Relevant Pages
|