Re: [boost] [Serialization] why operator &()?

Jim Hyslop wrote:

So who says they have to be chained? I agree the chained calls above look rather ugly, but what's wrong with:

a.serialize(member1); a.serialize(member2);

Clear, concise, and consistent.

I guess I just was just used to a different archiving system that used << and >> so it acted like streams, that the suggestion to replace both with a single & seemed logical and clean to me. I don't have any problem with the use of & in this context. FWIW, we don't chain calls together either as all our code is for XML archives which therefore has long make_nvp calls but I still prefer the & to a .serialize call. Must be just personal preference. Cheers Russell