Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

GNU sed 4.2.2 released; maintainer resigns

Posted Dec 26, 2012 20:17 UTC (Wed) by lu_zero (guest, #72556)
In reply to: GNU sed 4.2.2 released; maintainer resigns by Cyberax
Parent article: GNU sed 4.2.2 released; maintainer resigns

Everything is error prone then.

One of the issues I do have with C++ is that you must use a really strict subset (defeating the whole purpose of having such large standard library) in order to be reasonably sure your code will build and behave as you expect across different compiler/libstdc++ implementations.

And that because C++ is so complex and hard to implement that you have lots of interesting pitfalls.

(Log in to post comments)

GNU sed 4.2.2 released; maintainer resigns

Posted Dec 26, 2012 20:25 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]

Not everything, only the stuff that humans do directly.

> One of the issues I do have with C++ is that you must use a really strict subset
The only reason is to avoid incomprehensibly complex code.

> (defeating the whole purpose of having such large standard library) in order to be reasonably sure your code will build and behave as you expect across different compiler/libstdc++ implementations.
That hasn't been true for ages. All modern STL implementations are reasonably compatible - you won't find problems with standard containers and algorithms.

GNU sed 4.2.2 released; maintainer resigns

Posted Dec 27, 2012 16:53 UTC (Thu) by bronson (subscriber, #4806) [Link]

> ... you must use a really strict subset in order to be reasonably sure your code will build and behave as you expect across different compiler/libstdc++ implementations.

To be fair, this is true of libc too. "Always use glibc" dodges the problem (and not very successfully since glibc has so many obscure, dark corners).