roxen.lists.pike.general
| Subject | Author | Date |
|---|---|---|
| Re: mapping & mapping, order of evaluation guaranteed? | Martin Stjernholm <mast[at]lysator[dot]liu[dot]se> | 26-01-2009 |
"Stephen R. van den Berg" <<srb[at]cuci.nl>> wrote:
> mapping a=([4:44,5:55]);
> mapping b=([5:66,7:77]);
> werror("%O\n",a&b);
> gives: 5: 66
> werror("%O\n",b&a);
> gives: 5: 55
>
> Can I actually count on the fact that it seems to preserve the values
> of the second mapping mentioned in the & operator?
Yes. It's well defined for all merge operations. Ought to be stated in
the docs..
|
||