> But if we accidentally started to depend on C++14, we probably should write > this down
Not knowingly, Longterm3 branch claims "avoiding C++14" but Mitchell could have made a mistake, but since he has retired the branch its not going to be fixed if something did sneak in. @b4n to explain, the 4.8 _compiler_ may be "full featured" but the standard library wasn't standards compliant for `std::string` until "In the GCC 5.1 release libstdc++ introduced a new library ABI that includes new implementations of std::string and std::list." so its egregious of GCC to claim its compliant when even something as common as `std::string` is not compliant in the associated library, so who knows what else isn't. I'll be ranting again in a minute because it has always irked me that GCC ignores the state of the standard library shipped with it, even though its required to make it work. :grin: @mckaygerhard "i'm tyred of that shit! "too old" is the compiler provided" is the reason for my gentle rant, its not so nice when people rant at you is it? So please don't swear, make demands, or demeaning statements in __bold__. As Geany is a volunteer project people contribute what they want to contribute, and things like that just make them want to not help you. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2731#issuecomment-764009485
