8 Apr
2010
8 Apr
'10
10:50 a.m.
Thanks Robert and Brian. We'll revisit migration to 1.41. Last time we tried 3/4 months back, got some static assertion (if I remember correctly) related to some unsigned and signed comparison coming from archive code. And that time since it's not a must and we didn't have much bandwidth, we left it out. So, just a quick question - was that static assertion due to improper usage of the library or it's some bug in serialization library? If it's due to wrong usage, can you point me to related section of the doc? Regards, ~ Soumen -- View this message in context: http://old.nabble.com/-Serialization--std%3A%3Aset%3Cstd%3A%3Astring%3E-rest... Sent from the Boost - Users mailing list archive at Nabble.com.