On Mar 6, 2006, at 2:40 PM, Antonio Piccolboni wrote:
Hi, I noticed that after a resize the storage order is reset to the default value. This is apparent not only printing the contents (see attached test case) but also by inspecting strides() directly. Not only this breaks my program, but the only way to set the storage order is apparently in the constructor and therefore resize becomes de facto unusable for non default storage orders, so I don't even have a workaround. I couldn't find anything regarding this in the docs. I believe this is a serious bug. Can anyone advise?
Antonio
Greetings Antonio, Indeed, this is a bug. I will shortly check a fix into the BOOST CVS. My apologies for letting this slip past. And thank you for making me aware of it. Cheers, ron