$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Joel de Guzman: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
- Previous message: Joel de Guzman: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
- In reply to: David Abrahams: "[boost] Re: Optional, tie, and iterator_adaptor"
- Next in thread: Brian McNamara: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
- Reply: Brian McNamara: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
David Abrahams <dave_at_[hidden]> wrote:
> "Joel de Guzman" <djowel_at_[hidden]> writes:
>
>> What I am trying very hard to say is to stick to only *ONE* interface
>> and one concept.
>
> Optional is a container. I've never seen a container in C++ which didn't
> have both a value interface and an element-access interface. How do
> you propose to achieve that with optional?
Do it the ref, tuple and variant way: get(). But get(), as an element-access interface,
should return a reference, not a pointer, as it does currently.
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
- Next message: Joel de Guzman: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
- Previous message: Joel de Guzman: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
- In reply to: David Abrahams: "[boost] Re: Optional, tie, and iterator_adaptor"
- Next in thread: Brian McNamara: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
- Reply: Brian McNamara: "Re: [boost] Re: Optional, tie, and iterator_adaptor"
$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-footer.inc");
?>