|
Boost : |
Subject: Re: [boost] [smart_ptr] make_shared_array/allocate_shared_arrayfunction templates
From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2009-11-09 11:59:21
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 09 November 2009, Peter Dimov wrote:
> Roman Kecher wrote:
> > Hi,
> > I'm suggesting to add the following function templates to allow easy,
> > exception-safe, creation of shared_array objects:
> >
> > - make_shared_array (very similar to make_shared which is used to
> > create a shared_ptr)
> > - allocate_shared_array (again, same functionality like
> > allocate_shared)
> >
> >
> > Is there any reason not to include these?
>
> No, there is no reason to not include them. We just need a volunteer. :-)
Is it allright if I fix the perfect forwarding bug
(https://svn.boost.org/trac/boost/ticket/2962) in make/allocate_shared before
it maybe gets copied into a make/allocate_shared_array? IIRC you expressed a
preference for using std::forward when I originally brought this up. Can I
just assume std::forward is available if the compiler supports rvalue
references? Ticket #3570 suggests this might be a problem with stlport
however.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkr4SmoACgkQ5vihyNWuA4VUYQCdHWDKjLvapj1q8aNQ0GjJxfxK
BbIAoLzhbWXF8tQVlMYcV8Azc8AnRDkK
=nGFi
-----END PGP SIGNATURE-----
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk