Re: [boost] [GSoC][Phoenix3] Regarding mutability of arguments passed to phoenix expressions

Subject: Re: [boost] [GSoC][Phoenix3] Regarding mutability of arguments passed to phoenix expressions
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-04-28 07:12:17

Thomas Heller wrote:
>
> Regarding arguments to phoenix expressions there are two
> possibilities.
> The first is: Arguments are mutable. The current phoenix is
> implemented to be able to this.
[snip]
> The other approach would follow a more functional programming
> style as the data will not be mutable
[snip]
> To get the mutability back into phoenix i propose the use of
> phoenix::ref.
>
> I favor the second approach. However, this would break API
> compatibility between the existing implementation.

I think default immutability is safer and less surprising; C++ uses copy-by-value by default.  Even if this breaks code, we are talking about the third generation of an as yet unofficial library.  Now's the time to do it.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.