Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > C++ Moderated > N2691 Inconsist...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 4 Topic 9774 of 9909
Post > Topic >>

N2691 Inconsistencies in construct_element requirements

by "Bo Persson" <bop@[EMAIL PROTECTED] > Jul 8, 2008 at 03:14 AM

In section 20.7.9 [construct.element] the Effects clause contains
(options 2 and 3):


- if constructible_with_allocator_prefix<T, A::inner_allocator_type,
Args...> is derived
from true_type,

    alloc.construct(alloc.address(r), allocator_arg_t,
alloc.inner_allocator(), args...)


- if constructible_with_allocator_suffix<T, A::inner_allocator_type,
Args...> is derived
from true_type,

    alloc.construct(alloc.address(r), args..., alloc.inner_allocator())


However, these constructible_with_allocator_prefix and
constructible_with_allocator_suffix are concept maps, and not traits
derivable from true_type. This makes the section unimplementable at
present.


Bo Persson


-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]
 




 4 Posts in Topic:
N2691 Inconsistencies in construct_element requirements
"Bo Persson" &l  2008-07-08 03:14:08 
Re: N2691 Inconsistencies in construct_element requirements
Alberto Ganesh Barbati &l  2008-07-08 15:28:04 
Re: N2691 Inconsistencies in construct_element requirements
"Bo Persson" &l  2008-07-08 20:27:17 
Re: N2691 Inconsistencies in construct_element requirements
Alberto Ganesh Barbati &l  2008-07-09 13:31:08 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Wed Aug 20 4:10:34 CDT 2008.