Matthew Towler wrote:
> int a, c;
> int& b = a;
> b = c; // error, as attempting to reseat the reference.
um.. That's not an error, it just doesn't do what you think it does. It
actually assigns the value of c to a.
--
Truth,
James Curran
www.noveltheory.com (personal)
www.njtheater.com (pro
Reece Dunn wrote:
> construct when passing values. This was because I had been looking at
> the spirit library and read
>T const & ref;
> as
>T & const ref;
To be clear, Spirit's convention is T const& ref.
Cheers,
--
Joel de Guzman
joel at boost-consulting.com
http://www.boost-consulti
Thanks for the responses to my question. My generic list formatting library
used the
const T & const ref;
construct when passing values. This was because I had been looking at the
spirit library and read
T const & ref;
as
T & const ref;
I then interpreted that in the way pointers and const
