[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-05 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 Jonathan Wakely changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-04 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 Elmar Stellnberger changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-04 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 --- Comment #10 from Elmar Stellnberger --- Created attachment 43557 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43557&action=edit fixed version of auxtypes.h which works under g++ and clang Well if I fix things for clang then the code

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-04 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 --- Comment #9 from Elmar Stellnberger --- I still do not understand why this constructor gets called: inline xstrbuf( base_str s ). If I use .as_const() the result should be an xstr_const : public xstr_abstract and not an xstr_mutable: public xs

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-04 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 --- Comment #8 from Elmar Stellnberger --- concerning comment #4: Why do I not get the warning of utf8len being used uninitialized? I have compiled with -Wall and -Wmaybe-uninitialized. This would not be the first time that g++ does not notify m

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 Jonathan Wakely changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 --- Comment #6 from Jonathan Wakely --- (In reply to Elmar Stellnberger from comment #0) > Things work well however if I use the standard constructor instead of an > assignment: > > inline xstrbuf( base_str_const s ) : base_str( > const_cast(s

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 --- Comment #3 from Elmar Stellnberger --- if I unify the implicit copy constructor with my own one then it also works for g++: xstr_mutable( const xstr& s ) : xstr(s) {}

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 --- Comment #2 from Elmar Stellnberger --- Princess17b29a just found out that the problem can be resolved by adding the const keyword to the constructor in line 233: inline xstrbuf( const xstrbuf& s ) ... ... as neither "xstrbuf( base_str_const s

[Bug c++/84667] unreasonable refusal to use assignment operator method

2018-03-02 Thread estellnb at elstel dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84667 Elmar Stellnberger changed: What|Removed |Added Attachment #43542|0 |1 is obsolete|