shall I understand that it is not compatible with 1.35 ?
No, because there is a bug in 1.35
Ok, thank you for this clear answer ! So (hopefully it is not a big issue in my case...) i will upgrade to 1.36 and give up a few old files... Or write a small utility to upgrade files...
From what I understood, the bug affects only the STL collections am I right ?
Actually only std::vector of builtin types
Which are it has to be said very commonly used types! It seems very worrying that 1.35 users are going to be deliberately broken to help out <= 1.34.1 users who were broken accidentally. Is there really no plan to help out users load their 1.35 files in 1.36? Even if this can't be rectified within the library through a workaround, maybe a more independent (standalone?) utility could be provided? I have no familiarity with the internals of the library but if there is some way I can help in this regard, I'd be happy to try. Pete Bartlett