David Abrahams [EMAIL PROTECTED] wrote:
Joel de Guzman [EMAIL PROTECTED] writes:
optionalT::reset ( T const ) ;
Does it matter what happens when T is an auto_ptr?
Hmmm, an optional auto_ptr. What an interesting mix. Well, I'm
not sure. Fernando?
--
Joel de Guzman
David Abrahams [EMAIL PROTECTED] wrote:
Jaakko Jarvi [EMAIL PROTECTED] writes:
I've noticed that call_traits doesn't support function references.
I'm not sure whether it makes sense to store function references in
optionals, though, but in any case.
Something like this fails:
typedef
Fernando Cacciola [EMAIL PROTECTED] wrote:
I'm way overprotective, I guess
(maybe it's because I'll be father for the first time
in a couple of months :-)
Congratulations!
The only remaining issue is the optional interface:
Currenty, there is the following:
optionalT::optional ( T
Hi again,
Take 2:
typedef typename call_traitsT::param_type
ctor_param;
typedef typename call_traitstypename remove_referenceT::type::param_type
assign_param;
typedef typename call_traitsT::reference
return_type;
optional(typename call_traitsT::param_type arg);
Joel de Guzman [EMAIL PROTECTED] wrote:
Hi again,
Take 2:
typedef typename call_traitsT::param_type
ctor_param;
typedef typename call_traitstypename
remove_referenceT::type::param_type assign_param;
typedef typename call_traitsT::reference
return_type;
I've noticed that call_traits doesn't support function references.
I'm not sure whether it makes sense to store function references in
optionals, though, but in any case.
Something like this fails:
typedef void (afuncref)(int);
typedef call_traitsafunc::reference t;
The problem is that the
