| |||||||||||||
GNU sed 4.2.2 released; maintainer resignsGNU sed 4.2.2 released; maintainer resignsPosted Dec 25, 2012 0:18 UTC (Tue) by Cyberax (✭ supporter ✭, #52523)In reply to: GNU sed 4.2.2 released; maintainer resigns by paulj Parent article: GNU sed 4.2.2 released; maintainer resigns
Well, yeah. You can do pretty much anything in C (except non-sjlj exceptions which require true compiler support), but you have to do it manually.
And that's the point - doing things manually is error-prone and code-bloating.
(Log in to post comments)
GNU sed 4.2.2 released; maintainer resigns Posted Dec 25, 2012 12:47 UTC (Tue) by paulj (subscriber, #341) [Link]
Having to create your own infrastructure - doing it manually - doesn't of course mean you have to do it manually from scratch at every point. You can re-use your infrastructure of course. It will take a little more typing than "}" though, sure. That needn't mean it's more error-prone though, imho.
GNU sed 4.2.2 released; maintainer resigns Posted Dec 25, 2012 21:35 UTC (Tue) by Cyberax (✭ supporter ✭, #52523) [Link]
Everything that is not automatic is error-prone. Especially in rarely-tested code paths.
GNU sed 4.2.2 released; maintainer resigns Posted Dec 26, 2012 20:17 UTC (Wed) by lu_zero (guest, #72556) [Link]
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.
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
> (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.
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).
|
|||||||||||||