------- Comment #5 from oakad at yahoo dot com 2010-07-16 19:21 ------- Why is rope super-legacy? It had not enough attention to it, true, but it's a very convenient class in certain cases.
Does the bug resolution means that no more changes/updates are expected for gcc supplied rope, so external implementation should be preferred? And if such is the case, shouldn't rope class be marked as deprecated, so that similar functionality class can be proposed for addition elsewhere, in boost, for instance? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44963
